[
https://issues.apache.org/jira/browse/HBASE-4188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13090625#comment-13090625
]
nkeywal commented on HBASE-4188:
--------------------------------
Yes, I would expect them to be the scenario with consistency between read
and flush mentioned in the bug
HBASE-4195<https://issues.apache.org/jira/browse/HBASE-4195>(and
already managed in
HBASE-2856 <https://issues.apache.org/jira/browse/HBASE-2856>). You can
check this by changing "int flushInterval = 10;" in the method
"testWritesWhileGetting", for example by setting it to 2 or 3. This should
increase the number of failure. As well, the MemStoreTS of the KV in error
will be 0 (it comes from a file). This error (or at least the error I
analyzed) comes from the fact that the flush is finished before the end of
the Store#next, and not directly to the MemStore.
A xarning as well the patch in
HBASE-4195<https://issues.apache.org/jira/browse/HBASE-4195>will
conflict with this one, because they both touch the "seek" & "reseek"
function (even if it is actually different parts that are modified). Nothing
complex, but I won't be able to do the followup on this until end of next
week.
> Make in-memory table scanning faster, part2 (continuation of hbase-1938)
> ------------------------------------------------------------------------
>
> Key: HBASE-4188
> URL: https://issues.apache.org/jira/browse/HBASE-4188
> Project: HBase
> Issue Type: Improvement
> Components: performance
> Reporter: stack
> Assignee: nkeywal
> Priority: Critical
> Fix For: 0.92.0
>
> Attachments: 4188-mssp.txt
>
>
> This issue is a continuation of hbase-1938 work (That issue is closed). This
> issue is about getting the last patch posted by nkeywal over in hbase-1938
> applied (assigned nkeywal since he's done the work).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
