You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@accumulo.apache.org by "Josh Elser (JIRA)" <ji...@apache.org> on 2015/02/18 02:24:13 UTC

[jira] [Resolved] (ACCUMULO-3600) ShellServerIT.deleteRows might fail

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

Josh Elser resolved ACCUMULO-3600.
----------------------------------
    Resolution: Fixed

> ShellServerIT.deleteRows might fail
> -----------------------------------
>
>                 Key: ACCUMULO-3600
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3600
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.6.1
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.7.0, 1.6.3
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Saw a failure in {{ShellServerIT#deleteRows}} where one tablet had 2 files instead of the expected one. The test roughly does the following:
> 1. Create a table
> 2. Add 2 splits to that table (3 tablets)
> 3. Add 10 records (split "evenly" across the tablets)
> 4. Flush the table (spill memory to disk)
> 5. Check that each tablet has one file.
> The problem with the test is that while step 3 is happening, one of the new tablets could be migrated to the other tablet server. This would cause a minc (and write a file). Step3 would eventually finish, and then step4 would cause another minc (and file) on the tablet that was migrated. This would result in two rfiles for the tablet instead of the expected one.
> Need to update the test so that it accounts for this possibility.



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