[
https://issues.apache.org/jira/browse/HBASE-15935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15366399#comment-15366399
]
Joseph commented on HBASE-15935:
--------------------------------
Oh kk, that makes sense. I guess talking with [~eclark] it was more about
testing HBase correctness with a concurrent read/write workload vs reading and
writing in different phrases (Loop). He also mentioned that this would allow us
to check for the immediate availability of data after we said we had "flushed"
it. I can add this in as a feature though, it makes sense. Thanks!
> Have a separate Walker task running concurrently with Generator
> ------------------------------------------------------------------
>
> Key: HBASE-15935
> URL: https://issues.apache.org/jira/browse/HBASE-15935
> Project: HBase
> Issue Type: Sub-task
> Components: integration tests
> Reporter: Joseph
> Assignee: Joseph
> Priority: Minor
> Attachments: HBASE-15935.patch
>
>
> Keep track of which linked lists have been flushed in an HBase table, so that
> we can concurrently Walk these lists during the Generation phase. This will
> allow us to test:
> 1. HBase under concurrent read/writes
> 2. Availability of data immediately after flushes (as opposed to waiting till
> the Verification phase)
> The review diff can be found at:
> https://reviews.apache.org/r/48294/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
