[
https://issues.apache.org/jira/browse/HDDS-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16548604#comment-16548604
]
Bharat Viswanadham edited comment on HDDS-252 at 7/19/18 12:22 AM:
---
Hi [~nandakumar131]
Thanks for the review.
Handled the case of adding a new disk to datanode, which will check for any
volume has version file, take the dnId from that version file and use the same
for the newly added disk.
And also added a check for dnId.
Attached patch v03
was (Author: bharatviswa):
Hi [~nandakumar131]
Thanks for the review.
Handled the case of adding a new disk to datanode, which will check for any
volume has version file, take the dnId from that version file and use the same
for the new volume.
And also added a check for dnId.
Attached patch v03
> Eliminate the datanode ID file
> --
>
> Key: HDDS-252
> URL: https://issues.apache.org/jira/browse/HDDS-252
> Project: Hadoop Distributed Data Store
> Issue Type: Improvement
>Reporter: Bharat Viswanadham
>Assignee: Bharat Viswanadham
>Priority: Major
> Fix For: 0.2.1
>
> Attachments: HDDS-252.00.patch, HDDS-252.01.patch, HDDS-252.02.patch,
> HDDS-252.03.patch
>
>
> This Jira is to remove the datanodeID file. After ContainerIO work (HDDS-48
> branch) is merged, we have a version file in each Volume which stores
> datanodeUuid and some additional fields in that file.
> And also if this disk containing datanodeId path is removed, that DN will now
> be unusable with current code.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
