[
https://issues.apache.org/jira/browse/RATIS-2040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Teng updated RATIS-2040:
-----------------------------
Description:
Originally, the PeerId generated in file new-raft-meta.conf by command
{code:java}
$ ratis sh local raftMetaConf -peers
<P0_HOST:P0_PORT,P1_HOST:P1_PORT,P2_HOST:P2_PORT> -path
<PARENT_PATH_OF_RAFT_META_CONF> {code}
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.
was:To fix/remove old peer information in raft-meta.conf. Provide a ratis
command to modify list of peers in raft-meta.conf.
> Fix RaftPeerId generated by command of "raftMetaConf" to use real PeerId
> ------------------------------------------------------------------------
>
> Key: RATIS-2040
> URL: https://issues.apache.org/jira/browse/RATIS-2040
> Project: Ratis
> Issue Type: Task
> Components: shell
> Reporter: Dave Teng
> Assignee: Dave Teng
> Priority: Major
>
> Originally, the PeerId generated in file new-raft-meta.conf by command
> {code:java}
> $ ratis sh local raftMetaConf -peers
> <P0_HOST:P0_PORT,P1_HOST:P1_PORT,P2_HOST:P2_PORT> -path
> <PARENT_PATH_OF_RAFT_META_CONF> {code}
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
