[
https://issues.apache.org/jira/browse/HDFS-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12973403#action_12973403
]
Todd Lipcon commented on HDFS-1547:
-----------------------------------
One thing I've thought about a few times that I think should be considered:
rather than having separate include/exclude/decom files, why not have one file
with a very simple .properties style format?
{code}
dn1 = active
dn2 = active
dn3 = decomission
dn4 = exclude
{code}
This way we don't have to enumerate all the combinatorics like "what if it's in
both include and exclude? what if it's in decomission but not include?"
> Improve decommission mechanism
> ------------------------------
>
> Key: HDFS-1547
> URL: https://issues.apache.org/jira/browse/HDFS-1547
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: name-node
> Affects Versions: 0.23.0
> Reporter: Suresh Srinivas
> Assignee: Suresh Srinivas
> Fix For: 0.23.0
>
>
> Current decommission mechanism driven using exclude file has several issues.
> This bug proposes some changes in the mechanism for better manageability. See
> the proposal in the next comment for more details.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
