You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Joseph (JIRA)" <ji...@apache.org> on 2016/06/17 23:38:05 UTC

[jira] [Commented] (HBASE-8700) IntegrationTestBigLinkedList can fail due to random number collision

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

Joseph commented on HBASE-8700:
-------------------------------

Hello I was just playing around with the IntegrationTestBigLinkedList and was wondering how you use command line to specify optional values outside of the IntegrationTestBase optionals? 

For example how do I specify the logging frequency of a Walker in command line?

Because when I run the following:
./hbase org.apache.hadoop.hbase.test.IntegrationTestBigLinkedList walker -l 1000

I receive:
Unrecognized option: org.apache.commons.cli.UnrecognizedOptionException: Unrecognized option: -l from the parser in processOptions()

Do I just have to register all possible optionals in an overridden addOptions method like in IntegrationTestReplication.addOptions()? 
Sorry I am pretty new to this and thanks!




> IntegrationTestBigLinkedList can fail due to random number collision
> --------------------------------------------------------------------
>
>                 Key: HBASE-8700
>                 URL: https://issues.apache.org/jira/browse/HBASE-8700
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>             Fix For: 0.95.2, 0.94.9
>
>         Attachments: HBASE-8700-0.94.patch, HBASE-8700-v0.patch, HBASE-8700-v1.patch
>
>
> The test can fail due to random number collision, claiming there are unreferenced elements for obvious reasons (we rewrite some link). Original Accumulo test has one-stage generation so it doesn't count unreferenced elements as failures, only undefined ones. With 200m longs out of half-long range the probability of collision is approx 0.2%.
> Moreover, without some way to debug, it's hard to debug what keys should be looked at in such cases



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)