RATIS-931. Fixed Add a raft group to all peers currently registered

[juaby]

fixed In the log service, when creating a log, add a raft group to all group peers, where the group peers are not all peers currently registered

[runzhiwang]

You can open a jira at https://issues.apache.org/jira/projects/RATIS/issues, and add the jira number in the Pull Request title.
Besides, the Pull Request title is also too long.

[joshelser]

Can we rename the member peers to be allKnownPeers or similar? Something to try to prevent such an error in the future.

What about a test? Did you try to write a unit test to catch this? I think having 4 available workers, create a log, and then look at the raft groups and see that it has 4 members instead of 3 would work.

[juaby]

Can we rename the member peers to be allKnownPeers or similar? Something to try to prevent such an error in the future.

What about a test? Did you try to write a unit test to catch this? I think having 4 available workers, create a log, and then look at the raft groups and see that it has 4 members instead of 3 would work.

Sorry, it took so long to reply to you. about the log service, it is okay to verify according to the document (because the number of worker nodes is equal to the number of new raft groups), but when more than 3 worker nodes are started, a log is created at the time, the metadata service will broadcast the addition of Raft groups to unnecessary nodes outside the new raft group.
Personal suggestion: Ratis server adds verification. when an additional raft group is received, verify that the new raft group members must contain the current working node