[HBASE-6280] why using treeMap at default implement with class Batch.Callback

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 0.92.0
• Component/s: Coprocessors

Environment

centos 6.2 hbase 0.92.0

• Assignee: Unassigned
• Reporter: qiujaiwei
• Created: 27/Jun/12 08:23
• Updated: 13/Jun/22 16:53
• Resolved: 29/Jan/13 19:13

Description

public <T extends CoprocessorProtocol, R> Map<byte[],R> coprocessorExec(
Class<T> protocol, byte[] startKey, byte[] endKey,
Batch.Call<T,R> callable)
throws IOException, Throwable {

final Map<byte[],R> results = new TreeMap<byte[],R>(
Bytes.BYTES_COMPARATOR);
coprocessorExec(protocol, startKey, endKey, callable,
new Batch.Callback<R>(){
public void update(byte[] region, byte[] row, R value)

{ results.put(region, value); }

});
return results;
}

when mulit region call the Batch.Callback ,the treemap should lockup.
we meet this situation after we run 3 month.

Issue Links

• duplicates: HBASE-6565 Coprocessor exec result Map is not thread safe