[
https://issues.apache.org/jira/browse/HBASE-5121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13180279#comment-13180279
]
Zhihong Yu commented on HBASE-5121:
-----------------------------------
>From https://builds.apache.org/job/PreCommit-HBASE-Build/672/console:
{code}
HBASE-5121 patch is being downloaded at Thu Jan 5 10:51:42 UTC 2012 from
http://issues.apache.org/jira/secure/attachment/12509522/hbase-5121-testcase.patch
{code}
In the future, please attach the patch with solution last so that Hadoop QA can
pick up.
> MajorCompaction may affect scan's correctness
> ---------------------------------------------
>
> Key: HBASE-5121
> URL: https://issues.apache.org/jira/browse/HBASE-5121
> Project: HBase
> Issue Type: Bug
> Components: regionserver
> Reporter: chunhui shen
> Assignee: chunhui shen
> Attachments: hbase-5121-testcase.patch, hbase-5121.patch,
> hbase-5121v2.patch
>
>
> In our test, there are two families' keyvalue for one row.
> But we could find a infrequent problem when doing scan's next if
> majorCompaction happens concurrently.
> In the client's two continuous doing scan.next():
> 1.First time, scan's next returns the result where family A is null.
> 2.Second time, scan's next returns the result where family B is null.
> The two next()'s result have the same row.
> If there are more families, I think the scenario will be more strange...
> We find the reason is that storescanner.peek() is changed after
> majorCompaction if there are delete type KeyValue.
> This change causes the PriorityQueue<KeyValueScanner> of RegionScanner's heap
> is not sure to be sorted.
--
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
