In the current membership change implementation, we don't have persistent member information. After the membership change occurs, the node restarts, and the configuration information it uses may be incorrect, so we need to persist the member information, and update the persistence content when the membership change, if the member information is already in the store when the node starts, then use it directly
Version
0.6.0 (Default)
Relevant log output
No response
Code of Conduct
[X] I agree to follow this project's Code of Conduct
Description about the bug
In the current membership change implementation, we don't have persistent member information. After the membership change occurs, the node restarts, and the configuration information it uses may be incorrect, so we need to persist the member information, and update the persistence content when the membership change, if the member information is already in the store when the node starts, then use it directly
Version
0.6.0 (Default)
Relevant log output
No response
Code of Conduct