[jira] [Comment Edited] (HBASE-15935) Have a separate Walker task running concurrently with Generator

["Joseph (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/HBASE-15935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15365289#comment-15365289 ] 

Joseph edited comment on HBASE-15935 at 7/6/16 11:03 PM:
---------------------------------------------------------

The walker will cause the Generation phase to fail if it finds an anomaly. Counters are also kept during the Generation phase that count the number of bad nodes (either a non-existent node or a terminating one) it encountered in a loop. In general, it prints the same debugging information as the original Walker tool.


was (Author: vegetable26):
The walker will cause the Generation phase to fail if it finds an anomaly. Counters are also kept during the Generation phase that count the number of "bad" nodes. In general, it prints the same debugging information as the original Walker tool.

> 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)