Details
-
Type:
Bug
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: None
-
Fix Version/s: 5.5.32-galera
-
Component/s: None
-
Labels:
Description
WSREP_DEBUG_PRINT seems to be defined unconditionally, so even in a release build the server error log gets flooded with information which is presumably supposed to assist Galera debugging, e.g.
Exclusive conn 13, trx 2374, keylen 5, table table0_int_autoinc 0, 27, 1, 0, 0, Exclusive conn 11, trx 2302, keylen 5, table table0_int_autoinc 0, 2A, 1, 0, 0, Exclusive conn 13, trx 2374, keylen 5, table table0_key_pk_parts_2_int_autoinc 0, AF, 0, 0, 0, Exclusive conn 13, trx 2374, keylen 5, table table0_key_pk_parts_2_int_autoinc 0, B2, 0, 0, 0, Exclusive conn 11, trx 2302, keylen 5, table table0_key_pk_parts_2_int_autoinc 0, B5, 0, 0, 0, Exclusive conn 11, trx 2302, keylen 5, table table1_key_pk_parts_2_int_autoinc 0, 9, 1, 0, 0, Exclusive conn 11, trx 2302, keylen 5, table table1_key_pk_parts_2_int_autoinc 0, C, 1, 0, 0, Exclusive conn 11, trx 2302, keylen 5, table table1_key_pk_parts_2_int_autoinc 0, F, 1, 0, 0, Exclusive conn 11, trx 2302, keylen 5, table table1_key_pk_parts_2_int_autoinc 0, 30, 1, 0, 0, Exclusive conn 11, trx 2302, keylen 5, table table1_key_pk_parts_2_int_autoinc 0, 3F, 1, 0, 0,
etc.
After a 5-min moderate concurrent test (8 threads only), I got 10 MB error log file.
Gliffy Diagrams
Attachments
Activity
- All
- Comments
- Work Log
- History
- Activity
- Transitions
OooopS! fixed now at revision: http://bazaar.launchpad.net/~maria-captains/maria/maria-5.5-galera/revision/3407