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

Hudson commented on HDDS-1053:
------------------------------

SUCCESS: Integrated in Jenkins build Hadoop-trunk-Commit #16009 (See 
[https://builds.apache.org/job/Hadoop-trunk-Commit/16009/])
HDDS-1053. Generate RaftGroupId from OMServiceID. Contributed by (arp: rev 
676a9cb8888bfa80e8eeeda7a272971e1b3354f8)
* (edit) 
hadoop-ozone/ozone-manager/src/test/java/org/apache/hadoop/ozone/om/ratis/TestOzoneManagerRatisServer.java
* (edit) 
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/ratis/OzoneManagerRatisServer.java
* (edit) 
hadoop-hdds/common/src/main/java/org/apache/hadoop/ozone/OzoneConsts.java


> Generate RaftGroupId from OMServiceID
> -------------------------------------
>
>                 Key: HDDS-1053
>                 URL: https://issues.apache.org/jira/browse/HDDS-1053
>             Project: Hadoop Distributed Data Store
>          Issue Type: Sub-task
>            Reporter: Hanisha Koneru
>            Assignee: Aravindan Vijayan
>            Priority: Major
>             Fix For: 0.4.0
>
>         Attachments: HDDS-1053-000.patch, HDDS-1053-001.patch, 
> HDDS-1053-002.patch, HDDS-1053-003.patch, HDDS-1053-004.patch
>
>
> Ratis requires {{RaftGroupId}} to be a UUID. We need to generate this ID from 
> the {{OMServiceID}} so that it is consistent across all the OM nodes in a HA 
> service.
> Currently, we expect {{OMServiceId}} to be a 16 character string so that it 
> can be converted to a UUID. But {{OMServiceID}} is a user configurable 
> setting. Hence we cannot force users to input a 16 character string.
> One option is to hash the \{{OMServiceID}} string then truncate to UUID 
> length and use that to generate the UUID.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to