accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Created] (ACCUMULO-3974) Modify Randomwalk Bulk module to catch ACCUMULO-3967
Date Tue, 25 Aug 2015 19:27:45 GMT
Josh Elser created ACCUMULO-3974:
------------------------------------

             Summary: Modify Randomwalk Bulk module to catch ACCUMULO-3967
                 Key: ACCUMULO-3974
                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3974
             Project: Accumulo
          Issue Type: Bug
          Components: t, test
            Reporter: Josh Elser
            Priority: Critical
             Fix For: 1.6.4, 1.7.1, 1.8.0


[~ecn] asked me after I committed a fix for ACCUMULO-3967 "why didn't randomwalk catch this
bug?"

I think we could potentially have caught this if in Setup we pre-split the table to be a large
collection of sequentially increasing tablets. It's not a guarantee catch (since the bug itself
was only shown in the case of import failures and the tablet distribution hasn't changed).

Alternatively, we could copy the existing bulk module into a new module. In this module, we
remove the splitting and merging, instead keeping a static split distribution. This would
be almost guaranteed to eventually recreate the scenario. Adding in a chaotic balancer, even
more likely to reproduce.



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

Mime
View raw message