You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2022/12/21 08:02:00 UTC

[jira] [Commented] (HDDS-5934) Add OM NodeID to VERSION file

    [ https://issues.apache.org/jira/browse/HDDS-5934?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17650199#comment-17650199 ] 

mingchao zhao commented on HDDS-5934:
-------------------------------------

Ozone 1.3.0 had been released and we currently have more than 600 open issues targeted for 1.3.0. I am moving the target field to 1.4.0.

If there is anything needs to be discussed about the Target Version, Please reach out to me via Apache email or Slack.

> Add OM NodeID to VERSION file
> -----------------------------
>
>                 Key: HDDS-5934
>                 URL: https://issues.apache.org/jira/browse/HDDS-5934
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: Hanisha Koneru
>            Assignee: Hanisha Koneru
>            Priority: Major
>              Labels: pull-request-available
>
> OM uses its NodeID to generate the RaftPeerId. As such, the OM NodeId should be immutable. This Jira proposes to add the OM NodeId to its VERSION file. On restarts, the OM NodeID should be compared with the nodeId in the VERSION file to verify that it has not been updated. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org