[
https://issues.apache.org/jira/browse/ACCUMULO-3601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14329822#comment-14329822
]
Eric Newton commented on ACCUMULO-3601:
---------------------------------------
There's very little harm in letting the master knowing the status of a tablet.
Let's say we have a migration that intersects with a table delete. Let the
master handle the conflict.
> 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
>
> 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)
