kaijchen commented on PR #808: URL: https://github.com/apache/ratis/pull/808#issuecomment-1431023761
> * If the target peer already has the highest priority, do not call `setConfiguration`. > * If not, call `setConfiguration` to change only the target peer to the highest priority. > > Does it sound good? Yes. But how do we deal with old server (backward compatibility)? For example, for new servers, we don't need to change priority in the following situation. But for old servers, we have to increase target peer's priority to 2. | Peer | A | B | C | D | E | | --- | --- | --- | --- | --- | --- | | Priority | 1 | 1 | 1 | 1 | 1 | -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
