hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Phabricator (Updated) (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HBASE-5557) [89-fb] Fix incorrect reader/writer thread interaction in HBaseTest
Date Fri, 09 Mar 2012 23:18:59 GMT

     [ https://issues.apache.org/jira/browse/HBASE-5557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Phabricator updated HBASE-5557:
-------------------------------

    Attachment: D2235.1.patch

mbautin requested code review of "[jira] [HBASE-5557] [89-fb] Fix incorrect reader/writer
thread interaction in HBaseTest".
Reviewers: Kannan, JIRA, Karthik, Liyin

  Fixing an error in the 89-fb version of the single-client HBase load test (HBaseTest) where
the reader thread can attempt to read key #0 before it has been written.

TEST PLAN
  Run HBaseTest on a new table

REVISION DETAIL
  https://reviews.facebook.net/D2235

AFFECTED FILES
  src/test/java/org/apache/hadoop/hbase/manual/utils/MultiThreadedReader.java

MANAGE HERALD DIFFERENTIAL RULES
  https://reviews.facebook.net/herald/view/differential/

WHY DID I GET THIS EMAIL?
  https://reviews.facebook.net/herald/transcript/4905/

Tip: use the X-Herald-Rules header to filter Herald messages in your client.

                
> [89-fb] Fix incorrect reader/writer thread interaction in HBaseTest
> -------------------------------------------------------------------
>
>                 Key: HBASE-5557
>                 URL: https://issues.apache.org/jira/browse/HBASE-5557
>             Project: HBase
>          Issue Type: Bug
>    Affects Versions: 0.89-fb
>            Reporter: Mikhail Bautin
>            Assignee: Mikhail Bautin
>            Priority: Minor
>         Attachments: D2235.1.patch
>
>
> In the HBaseTest load test we have a condition when the writer has not written any keys
but the reader might attempt to read key 0, resulting in a failure. This bug is specific to
89-fb because it has been fixed while open-sourcing HBaseTest as LoadTestTool, and those improvements
still have not been back-ported to 89-fb. Doing a temporary fix now and we will get to the
back-port later. 
> 12/03/09 14:12:52 INFO utils.MultiThreadedReader: Key = cfcd208495d565ef66e7dff9f98764da:0
> 12/03/09 14:12:52 ERROR utils.MultiThreadedReader: No data returned, tried to get actions
for key = cfcd208495d565ef66e7dff9f98764da:0
> 12/03/09 14:12:52 INFO utils.MultiThreadedReader: Key = cfcd208495d565ef66e7dff9f98764da:0
> 12/03/09 14:12:52 INFO utils.MultiThreadedReader: Key = cfcd208495d565ef66e7dff9f98764da:0
> 12/03/09 14:12:52 ERROR utils.MultiThreadedReader: No data returned, tried to get actions
for key = cfcd208495d565ef66e7dff9f98764da:0
> 12/03/09 14:12:52 ERROR utils.MultiThreadedReader: No data returned, tried to get actions
for key = cfcd208495d565ef66e7dff9f98764da:0
> 12/03/09 14:12:52 INFO utils.MultiThreadedReader: Key = cfcd208495d565ef66e7dff9f98764da:0
> 12/03/09 14:12:52 ERROR utils.MultiThreadedReader: No data returned, tried to get actions
for key = cfcd208495d565ef66e7dff9f98764da:0
> 12/03/09 14:12:52 ERROR utils.MultiThreadedReader: Aborting run -- found more than three
errors

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

        

Mime
View raw message