hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Gary Helmling (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (HBASE-6280) why using treeMap at default implement with class Batch.Callback
Date Tue, 29 Jan 2013 19:13:15 GMT

     [ https://issues.apache.org/jira/browse/HBASE-6280?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Gary Helmling resolved HBASE-6280.
----------------------------------

    Resolution: Duplicate

This was resolved in HBASE-6565, included in 0.92.2.
                
> why using treeMap at default implement with class  Batch.Callback
> -----------------------------------------------------------------
>
>                 Key: HBASE-6280
>                 URL: https://issues.apache.org/jira/browse/HBASE-6280
>             Project: HBase
>          Issue Type: Bug
>          Components: Coprocessors
>    Affects Versions: 0.92.0
>         Environment: centos 6.2 hbase 0.92.0
>            Reporter: qiujaiwei
>
> 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.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message