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] [Updated] (ACCUMULO-3601) master does not process migrations
Date Sat, 21 Feb 2015 02:48:12 GMT

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

Josh Elser updated ACCUMULO-3601:
---------------------------------
    Attachment: 0001-ACCUMULO-3601-Must-synchronize-on-instance-to-iterat.patch

Simple patch that addresses the synchornization (which I think is necessary). ACCUMULO-3609
has a patch which unbreaks the tests that were not running correctly for me.

> master does not process migrations
> ----------------------------------
>
>                 Key: ACCUMULO-3601
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3601
>             Project: Accumulo
>          Issue Type: Bug
>          Components: master
>            Reporter: Eric Newton
>            Assignee: Eric Newton
>            Priority: Blocker
>             Fix For: 1.5.3, 1.7.0, 1.6.3
>
>         Attachments: 0001-ACCUMULO-3601-Must-synchronize-on-instance-to-iterat.patch
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> While attempting to write a test for ACCUMULO-3597, I found the master was not balancing.
 The iterator that filters the metadata table does not take migrations into account, so the
state of the tablets was never seen, and processed.  This bug was introduced with the fix
to ACCUMULO-3580.



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

Mime
View raw message