Description
Originally, the PeerId generated in file new-raft-meta.conf by command
$ ratis sh local raftMetaConf -peers <P0_HOST:P0_PORT,P1_HOST:P1_PORT,P2_HOST:P2_PORT> -path <PARENT_PATH_OF_RAFT_META_CONF>
it uses the address of server as PeerId, which would cause the ratis group to fail to start if there are some duplicated addresses stored in raft-meta.conf.
Thus, need to fix that by using actual PeerId in raft-meta.conf and store back to generated new-raft-meta.conf.
Attachments
Issue Links
- is related to
-
HDDS-10509 Allow running ratis shell commands in secure Ozone cluster.
- Open
-
HDDS-10479 Fix RaftPeerId generated by command of "raftMetaConf" to use real PeerId
- Resolved
-
RATIS-2069 RaftMetaConf command sets incorrect peerAddress pattern.
- Resolved
-
RATIS-1860 Add ratis-shell cmd to generate a new raft-meta.conf.
- Resolved