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.
|Field||Original Value||New Value|
|Component/s||Performance [ 12314193 ]|
|Status||Open [ 1 ]||Resolved [ 5 ]|
|Resolution||Fixed [ 1 ]|
|Summary||HTable.batch does not have to synchronized||HTable.batch does not have to be synchronized|
|Status||Resolved [ 5 ]||Closed [ 6 ]|