You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Yuan Kang (JIRA)" <ji...@apache.org> on 2012/08/13 08:20:37 UTC
[jira] [Created] (HBASE-6565) hbase coprocessor return the
Map object sometimes have a wrong size
Yuan Kang created HBASE-6565:
--------------------------------
Summary: hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size
Key: HBASE-6565
URL: https://issues.apache.org/jira/browse/HBASE-6565
Project: HBase
Issue Type: Bug
Components: client
Affects Versions: 0.94.0
Environment: hadoop1.0.2,hbase0.94,jdk1.6
Reporter: Yuan Kang
I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13448335#comment-13448335 ]
Hudson commented on HBASE-6565:
-------------------------------
Integrated in HBase-0.94-security-on-Hadoop-23 #7 (See [https://builds.apache.org/job/HBase-0.94-security-on-Hadoop-23/7/])
HBASE-6565. Coprocessor exec result Map is not thread safe (Yuan Kang) (Revision 1373975)
Result = FAILURE
apurtell :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
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
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436155#comment-13436155 ]
stack commented on HBASE-6565:
------------------------------
@Andrew OK. Thanks.
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Gary Helmling (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436169#comment-13436169 ]
Gary Helmling commented on HBASE-6565:
--------------------------------------
Ran TestCoprocessorEndpoint on trunk 100 times with the patch applied and testAggregation() re-enabled. No failures. Previously testAggregation() would fail reliably withing ~50 runs. Looks like this patch fixes the issue.
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6565) hbase coprocessor return the
Map object sometimes have a wrong size
Posted by "Yuan Kang (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yuan Kang updated HBASE-6565:
-----------------------------
Attachment: Coprocessor-result-thread unsafe-bug-fix.patch
the patch can fix the bug when test is done
> hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size
> -----------------------------------------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.94.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: patch
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Assigned] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Zhihong Ted Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhihong Ted Yu reassigned HBASE-6565:
-------------------------------------
Assignee: Yuan Kang
Nice catch, Yuan.
Assigning issue to you.
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.96.0, 0.92.3, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-6565:
----------------------------------
Component/s: coprocessors
Affects Version/s: 0.96.0
0.92.2
Fix Version/s: 0.92.2
Summary: Coprocessor exec result Map is not thread safe (was: hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size)
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Zhihong Ted Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436090#comment-13436090 ]
Zhihong Ted Yu commented on HBASE-6565:
---------------------------------------
@Andy:
Fix version for 0.92 should be 0.92.3, I think.
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436150#comment-13436150 ]
Andrew Purtell commented on HBASE-6565:
---------------------------------------
@stack It hasn't been committed yet, still waiting for 100 consecutive runs to pass, but I expect it to go in, will commit on 0.92 branch too.
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
stack updated HBASE-6565:
-------------------------
Fix Version/s: (was: 0.92.3)
0.92.2
Marking as 0.92.2 since this patch has been applied to 0.92 branch and 0.92.2 is not yet released.
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) hbase coprocessor return the
Map object sometimes have a wrong size
Posted by "stack (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13433233#comment-13433233 ]
stack commented on HBASE-6565:
------------------------------
@Yuan HTable is not really thread safe. See the class comment. Given that should we apply this patch?
> hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size
> -----------------------------------------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.94.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: patch
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13439511#comment-13439511 ]
Hudson commented on HBASE-6565:
-------------------------------
Integrated in HBase-0.94-security #48 (See [https://builds.apache.org/job/HBase-0.94-security/48/])
HBASE-6565. Coprocessor exec result Map is not thread safe (Yuan Kang) (Revision 1373975)
Result = FAILURE
apurtell :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) hbase coprocessor return the
Map object sometimes have a wrong size
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432970#comment-13432970 ]
Hadoop QA commented on HBASE-6565:
----------------------------------
-1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12540615/Coprocessor-result-thread%20unsafe-bug-fix.patch
against trunk revision .
+1 @author. The patch does not contain any @author tags.
-1 tests included. The patch doesn't appear to include any new or modified tests.
Please justify why no new tests are needed for this patch.
Also please list what manual steps were performed to verify this patch.
-1 patch. The patch command could not apply the patch.
Console output: https://builds.apache.org/job/PreCommit-HBASE-Build/2554//console
This message is automatically generated.
> hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size
> -----------------------------------------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.94.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: patch
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436437#comment-13436437 ]
Hudson commented on HBASE-6565:
-------------------------------
Integrated in HBase-TRUNK-on-Hadoop-2.0.0 #132 (See [https://builds.apache.org/job/HBase-TRUNK-on-Hadoop-2.0.0/132/])
HBASE-6565. Coprocessor exec result Map is not thread safe (Yuan Kang) (Revision 1373972)
Result = FAILURE
apurtell :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-6565:
----------------------------------
Fix Version/s: (was: 0.92.2)
0.92.3
@Ted updated fix version for 0.92, thanks!
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.96.0, 0.92.3, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6565) hbase coprocessor return the
Map object sometimes have a wrong size
Posted by "Zhihong Ted Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhihong Ted Yu updated HBASE-6565:
----------------------------------
Status: Patch Available (was: Open)
> hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size
> -----------------------------------------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.94.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: patch
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Gary Helmling (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436095#comment-13436095 ]
Gary Helmling commented on HBASE-6565:
--------------------------------------
I'm betting this fixes TestCoprocessorEndpoint#testAggregation, which was previously flaky. Should have seen this much sooner.
I'm running TestCoprocessorEndpoint on trunk with the patch applied in a loop of 100 times to confirm.
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) hbase coprocessor return the
Map object sometimes have a wrong size
Posted by "Gary Helmling (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434828#comment-13434828 ]
Gary Helmling commented on HBASE-6565:
--------------------------------------
@Stack - this is needed because the TreeMap is referenced in the Callback that is pushed down into the Callable run in the HTable thread pool. Definitely an important fix.
> hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size
> -----------------------------------------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.94.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: patch
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) hbase coprocessor return the
Map object sometimes have a wrong size
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13435755#comment-13435755 ]
Andrew Purtell commented on HBASE-6565:
---------------------------------------
Ok will commit this tomorrow if no objection.
> hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size
> -----------------------------------------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.94.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: patch
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440151#comment-13440151 ]
Hudson commented on HBASE-6565:
-------------------------------
Integrated in HBase-0.92-security #116 (See [https://builds.apache.org/job/HBase-0.92-security/116/])
HBASE-6565. Coprocessor exec result Map is not thread safe (Yuan Kang) (Revision 1373976)
Result = FAILURE
apurtell :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6565) hbase coprocessor return the
Map object sometimes have a wrong size
Posted by "Zhihong Ted Yu (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zhihong Ted Yu updated HBASE-6565:
----------------------------------
Release Note: (was: fix a bug in coprocessor )
@Yuan:
Bug fix doesn't need release note.
> hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size
> -----------------------------------------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.94.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: patch
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436258#comment-13436258 ]
Hudson commented on HBASE-6565:
-------------------------------
Integrated in HBase-TRUNK #3227 (See [https://builds.apache.org/job/HBase-TRUNK/3227/])
HBASE-6565. Coprocessor exec result Map is not thread safe (Yuan Kang) (Revision 1373972)
Result = FAILURE
apurtell :
Files :
* /hbase/trunk/hbase-server/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436268#comment-13436268 ]
Hudson commented on HBASE-6565:
-------------------------------
Integrated in HBase-0.94 #401 (See [https://builds.apache.org/job/HBase-0.94/401/])
HBASE-6565. Coprocessor exec result Map is not thread safe (Yuan Kang) (Revision 1373975)
Result = SUCCESS
apurtell :
Files :
* /hbase/branches/0.94/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6565) hbase coprocessor return the
Map object sometimes have a wrong size
Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lars Hofhansl updated HBASE-6565:
---------------------------------
Fix Version/s: 0.94.2
0.96.0
> hbase coprocessor return the Map<byte[],R> object sometimes have a wrong size
> -----------------------------------------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client
> Affects Versions: 0.94.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436116#comment-13436116 ]
Andrew Purtell commented on HBASE-6565:
---------------------------------------
@Gary, yes doing that here too precommit. Please put up your results too.
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.96.0, 0.92.3, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Gary Helmling (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436172#comment-13436172 ]
Gary Helmling commented on HBASE-6565:
--------------------------------------
So, just to be clear, big +1 from me. Thanks Yuan!
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436321#comment-13436321 ]
Hudson commented on HBASE-6565:
-------------------------------
Integrated in HBase-0.92 #493 (See [https://builds.apache.org/job/HBase-0.92/493/])
HBASE-6565. Coprocessor exec result Map is not thread safe (Yuan Kang) (Revision 1373976)
Result = SUCCESS
apurtell :
Files :
* /hbase/branches/0.92/CHANGES.txt
* /hbase/branches/0.92/src/main/java/org/apache/hadoop/hbase/client/HTable.java
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13436173#comment-13436173 ]
Andrew Purtell commented on HBASE-6565:
---------------------------------------
Thanks Gary.
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (HBASE-6565) Coprocessor exec result Map is not
thread safe
Posted by "Andrew Purtell (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/HBASE-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Purtell updated HBASE-6565:
----------------------------------
Tags: coprocessor (was: coprocessor HTable)
Resolution: Fixed
Hadoop Flags: Reviewed
Status: Resolved (was: Patch Available)
Committed to trunk, 0.94, and 0.92 branches. TestCoprocessorEndpoint passes 100 times consecutively locally. Thanks for the patch Yuan.
> Coprocessor exec result Map is not thread safe
> ----------------------------------------------
>
> Key: HBASE-6565
> URL: https://issues.apache.org/jira/browse/HBASE-6565
> Project: HBase
> Issue Type: Bug
> Components: client, coprocessors
> Affects Versions: 0.92.2, 0.94.0, 0.96.0
> Environment: hadoop1.0.2,hbase0.94,jdk1.6
> Reporter: Yuan Kang
> Assignee: Yuan Kang
> Labels: coprocessors, patch
> Fix For: 0.92.2, 0.96.0, 0.94.2
>
> Attachments: Coprocessor-result-thread unsafe-bug-fix.patch
>
> Original Estimate: 168h
> Remaining Estimate: 168h
>
> I develop a coprocessor program ,but found some different results in repeated tests.for example,normally,the result's size is 10.but sometimes it appears 9.
> I read the HTable.java code,found a TreeMap(thread-unsafe) be used in multithreading environment.It cause the bug happened
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira