[
https://issues.apache.org/jira/browse/HDDS-1266?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16815514#comment-16815514
]
Yiqun Lin commented on HDDS-1266:
---------------------------------
Thanks for the comments, [~anu].
{quote}[~ccondit] had suggested that one way to solve that problem is to listen
to the changes via Journal Node
{quote}
To listen the changes via Journal Node seems a reasonable approach.
Another aspect I forget to mention in my last comment, the doc has designed a
lot about how to do the upgrade but how the downgrade behavior it will be? If
the block mapping process is not our expected, we want to downgrade this. What
OM, SCM service will do? Deleting created containers in DNs and related
metadata db files?
> [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]
