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] [Resolved] (ACCUMULO-3838) ReplicationIT.replicationEntriesPrecludeWalDeletion failed because it missed an expected WAL
Date Thu, 21 May 2015 04:05:00 GMT

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

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

Work around the test failure by checking both the replication table and the metadata table.

Add in some extra debugging for the future and removed some unused code.

> ReplicationIT.replicationEntriesPrecludeWalDeletion failed because it missed an expected
WAL
> --------------------------------------------------------------------------------------------
>
>                 Key: ACCUMULO-3838
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3838
>             Project: Accumulo
>          Issue Type: Bug
>          Components: test
>    Affects Versions: 1.7.0
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Minor
>             Fix For: 1.8.0, 1.7.1
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> Automated testing found a situation where we have 4 WALs in the replication table, but
only expected to find 3. Thus, the test failed.
> Looking at the master log, there shouldn't be any way that the test _didn't_ see this
log. My hunch is that the test accidentally removed one of the logs that should have been
left in the expected set.
> Need to revisit the logic to make sure it's solid.



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

Mime
View raw message