[
https://issues.apache.org/jira/browse/ACCUMULO-4004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15217383#comment-15217383
]
Josh Elser commented on ACCUMULO-4004:
--------------------------------------
bq. Some folks I'm working with have been wanting this to make replication more
predictive.
Definitely a nice bonus which gets around a quick of the replication impl.
bq. It should be possible to manually roll WALs so that files on
decommissioning datanodes are closed and the decommissioning process can
complete
[~ecn], do you have an explanation for why we even need to do this? I'd like to
better understand why we need to change our code.
> open WALs prevent DN decommissioning
> ------------------------------------
>
> Key: ACCUMULO-4004
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4004
> Project: Accumulo
> Issue Type: Improvement
> Components: tserver
> Reporter: Eric Newton
> Assignee: Eric Newton
> Fix For: 1.6.6, 1.7.2, 1.8.0
>
> Attachments: ACCUMULO-4004-1.patch
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> It should be possible to manually roll WALs so that files on decommissioning
> datanodes are closed and the decommissioning process can complete. At the
> very least, the logs could be closed after an elapsed period of time, such as
> an hour.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
