[
https://issues.apache.org/jira/browse/HDDS-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16814604#comment-16814604
]
Yiqun Lin commented on HDDS-1266:
---------------------------------
HI [~anu], the design doc looks interesting! Some comments from me:
When do the mapping for HDFS blockId to Ozone blockId, there is one
precondition that HDFS blockId should be unique. The HDFS block id is unique in
a single block pool (namepsace). But with multiple block pool case, I suppose
we cannot promise this.
>From the design doc, we cannot sync the metadata change between HDFS and Ozone
>during upgrade time. That is to say that for one system metadata change cannot
>reflect in another system. Based on this, seems we can't well supported
>concurrently running HDFS and Ozone to provider the service, except one case
>that we upgrade some specific HDFS folders that will only accessed by Ozone.
>So that currently we recommend that make HDFS downtime during upgrade, after
>upgrade we use the new system Ozone.
Please correct me If I am wrong, :).
> [Ozone upgrade] Support Upgrading HDFS clusters to use Ozone
> ------------------------------------------------------------
>
> Key: HDDS-1266
> URL: https://issues.apache.org/jira/browse/HDDS-1266
> Project: Hadoop Distributed Data Store
> Issue Type: New Feature
> Reporter: Anu Engineer
> Assignee: Anu Engineer
> Priority: Major
> Attachments: InPlaceUpgradesForOzone.pdf
>
>
> This is the master JIRA to support upgrading existing HDFS clusters to have
> Ozone running concurrently. One of the requirements is that we support
> upgrading from HDFS to Ozone, without a full data copy. This requirement is
> called "In Place upgrade", the end result of such an upgrade would be to have
> the HDFS data appear in Ozone as if Ozone has taken a snap-shot of the HDFS
> data. Once upgrade is complete, Ozone and HDFS will act as independent
> systems. I will post a design document soon.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
