Hi,
I notice that when I run db4.8tat -t the Active Transaction list does not change very often. I would have expected it to not be the same twice. So I guess I have a lot of stuck transactions?
I use back_hdb and slapd is under some load.
Could this be related to the messages in the log:
Dec 15 15:09:19 server1 slapd[32060]: => bdb_idl_delete_key: c_del id failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) Dec 15 15:09:19 server1 slapd[32060]: conn=40803 op=18: attribute "entryCSN" index delete failure
/Peter
Active transactions: 80000003: running; pid/thread 32060/47089260848688; begin LSN: file/offset 0/0 80000004: running; pid/thread 32060/47089260848688; begin LSN: file/offset 0/0 80000006: running; pid/thread 32060/1127287120; begin LSN: file/offset 0/0 80000007: running; pid/thread 32060/1110501712; begin LSN: file/offset 0/0 80000008: running; pid/thread 32060/1118894416; begin LSN: file/offset 0/0 8000006b: running; pid/thread 32060/1135679824; begin LSN: file/offset 0/0 8000006d: running; pid/thread 32060/1088940368; begin LSN: file/offset 0/0 80000076: running; pid/thread 32060/1144072528; begin LSN: file/offset 0/0 80000077: running; pid/thread 32060/1152465232; begin LSN: file/offset 0/0 8000007c: running; pid/thread 32060/1160857936; begin LSN: file/offset 0/0 80000081: running; pid/thread 32060/1169250640; begin LSN: file/offset 0/0 80000082: running; pid/thread 32060/1177643344; begin LSN: file/offset 0/0 800000b7: running; pid/thread 32060/1186036048; begin LSN: file/offset 0/0 ....
Peter Mogensen wrote:
Hi,
I notice that when I run db4.8tat -t the Active Transaction list does not change very often. I would have expected it to not be the same twice. So I guess I have a lot of stuck transactions?
No.
I use back_hdb and slapd is under some load.
Could this be related to the messages in the log:
No.
Dec 15 15:09:19 server1 slapd[32060]: => bdb_idl_delete_key: c_del id failed: DB_LOCK_DEADLOCK: Locker killed to resolve a deadlock (-30994) Dec 15 15:09:19 server1 slapd[32060]: conn=40803 op=18: attribute "entryCSN" index delete failure
Active transactions: 80000003: running; pid/thread 32060/47089260848688; begin LSN: file/offset 0/0 80000004: running; pid/thread 32060/47089260848688; begin LSN: file/offset 0/0 80000006: running; pid/thread 32060/1127287120; begin LSN: file/offset 0/0 80000007: running; pid/thread 32060/1110501712; begin LSN:
Notice that these TXNs all have empty file/offset, which means they have not generated any modifications. They are the long-lived read-only TXNs that back-bdb/hdb use for internal purposes. Completely normal.
Howard Chu wrote:
Notice that these TXNs all have empty file/offset, which means they have not generated any modifications. They are the long-lived read-only TXNs that back-bdb/hdb use for internal purposes. Completely normal.
Ok. Thanx for clearing that up.
They got me worried for at moment, since I discovered them while trying to figure out why the log contains "connection_input: conn=XXXX deferring operation: too many executing" messages.
I've looked all over the application and from what I can see I only use synchronous client API calls.
/Peter
openldap-technical@openldap.org