[
https://issues.apache.org/jira/browse/HDFS-3765?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13429651#comment-13429651
]
Todd Lipcon commented on HDFS-3765:
-----------------------------------
Code looks pretty reasonable. But I think we should separate this into two
separate patches. I'm not 100% convinced the "copy from one edits storage to
another" should be lumped in with "initializeSharedEdits". Would you mind doing
just the genericizing part in this JIRA and we can discuss the other use case
separately?
Also, please add a test which uses this new facility to initialize BKJM edits,
if you don't mind.
> Namenode INITIALIZESHAREDEDITS should be able to initialize all shared
> storages
> -------------------------------------------------------------------------------
>
> Key: HDFS-3765
> URL: https://issues.apache.org/jira/browse/HDFS-3765
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: ha
> Affects Versions: 2.1.0-alpha, 3.0.0
> Reporter: Vinay
> Assignee: Vinay
> Attachments: HDFS-3765.patch
>
>
> Currently, NameNode INITIALIZESHAREDEDITS provides ability to copy the edits
> files to file schema based shared storages when moving cluster from Non-HA
> environment to HA enabled environment.
> This Jira focuses on the following
> * Generalizing the logic of copying the edits to new shared storage so that
> any schema based shared storage can initialized for HA cluster.
> * Ability to Initialize new shared storage from existing shared storage when
> moving from One shared storage to another shared storage (Might be because of
> cost, performance, etc. For ex: Moving from NFS to BKJM/QJM).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
