[ 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