[
https://issues.apache.org/jira/browse/RATIS-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17251129#comment-17251129
]
runzhiwang edited comment on RATIS-1247 at 12/17/20, 2:40 PM:
--------------------------------------------------------------
bq. Now, support the servers have different priorities. If an admin tries to
failover from a higher priority server to a low a priority server, the failover
command should be rejected.
[~szetszwo] In my thinking, change priority can be a part of rolling upgrade.
For example. If we want to change leader from server1 to server2.
1. We upgrade server2 and assign server2 a higher priority.
2. Force server1 to stop accepting write request.
3. When server2's log catch up with server1, server2 will try to grab the
leader because server2's priority is higher.
#1 and #3 has been supported, we only need to do #2
what do you think ?
was (Author: yjxxtd):
bq. Now, support the servers have different priorities. If an admin tries to
failover from a higher priority server to a low a priority server, the failover
command should be rejected.
[~szetszwo] In my thinking, change priority can be a part of rolling upgrade.
For example. If we want to change leader from server1 to server2.
1. We upgrade server2 and assign server2 a higher priority. this step has been
supported.
2. Force server1 to stop accepting write request. we need to do this.
3. When server2's log catch up with server1, server2 will try to grab the
leader because server2's priority is higher. this step has been implemented
what do you think ?
> Support rolling upgrade and rollback
> ------------------------------------
>
> Key: RATIS-1247
> URL: https://issues.apache.org/jira/browse/RATIS-1247
> Project: Ratis
> Issue Type: Sub-task
> Reporter: runzhiwang
> Assignee: runzhiwang
> Priority: Major
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
