This was raised on the mailing list by Yousuf.
HTable.batch(...) is synchronized and there appears to be no reason for it.
(flushCommits makes the same call to connection.processBatch and it also is not synchronized)
This is pretty bad actually marking critical.
0.96 is fine BTW.
|Transition||Time In Source Status||Execution Times||Last Executer||Last Execution Date|
|13h 3m||1||Lars Hofhansl||30/Oct/12 18:10|
|34d 3h 36m||1||Lars Hofhansl||03/Dec/12 21:47|
|Status||Resolved [ 5 ]||Closed [ 6 ]|
|Summary||HTable.batch does not have to synchronized||HTable.batch does not have to be synchronized|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Field||Original Value||New Value|
|Component/s||Performance [ 12314193 ]|