You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
请问如何初始化raft集群时,对彼此的身份进行验证?然后进行增删节点时,该节点也必须是通过某种校验后,合法节点再纳入集群中。
When initializing a raft cluster, how to verify each other's identities? Then when adding or deleting nodes, the nodes must also pass some kind of verification before the legitimate nodes are included in the cluster.
Your scenes
防止生产环境中错误增加一个成员,比如ip错误,或者将其他的raft集群中的成员写入到该集群的成员中,以免造成一些未知影响,实际上应该不会有什么问题,只不过每次只有加入进去了,看日志才能看出来加入的节点有问题之类的,无法在调用changepeers,addpeers等等场景时,就能给出一个明确反馈该成员不合法的信息或异常。
To prevent errors in the production environment from adding a member, such as an incorrect IP or inadvertently adding a member from another Raft cluster to the current one, thereby avoiding potential unknown consequences. In reality, there shouldn't be any issues, but it's difficult to detect problems with newly added nodes until inspecting the logs. It's not feasible to provide immediate feedback indicating that a member is invalid when calling functions like changepeers or addpeers. However, it would be beneficial to have a clear indication or exception that the member is invalid.
Your advice
Environment
SOFAJRaft version:
JVM version (e.g. java -version):
OS version (e.g. uname -a):
Maven version:
IDE version:
The text was updated successfully, but these errors were encountered:
Your question
请问如何初始化raft集群时,对彼此的身份进行验证?然后进行增删节点时,该节点也必须是通过某种校验后,合法节点再纳入集群中。
When initializing a raft cluster, how to verify each other's identities? Then when adding or deleting nodes, the nodes must also pass some kind of verification before the legitimate nodes are included in the cluster.
Your scenes
防止生产环境中错误增加一个成员,比如ip错误,或者将其他的raft集群中的成员写入到该集群的成员中,以免造成一些未知影响,实际上应该不会有什么问题,只不过每次只有加入进去了,看日志才能看出来加入的节点有问题之类的,无法在调用changepeers,addpeers等等场景时,就能给出一个明确反馈该成员不合法的信息或异常。
To prevent errors in the production environment from adding a member, such as an incorrect IP or inadvertently adding a member from another Raft cluster to the current one, thereby avoiding potential unknown consequences. In reality, there shouldn't be any issues, but it's difficult to detect problems with newly added nodes until inspecting the logs. It's not feasible to provide immediate feedback indicating that a member is invalid when calling functions like changepeers or addpeers. However, it would be beneficial to have a clear indication or exception that the member is invalid.
Your advice
Environment
java -version
):uname -a
):The text was updated successfully, but these errors were encountered: