[
https://issues.apache.org/jira/browse/RATIS-1625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Riguz Lee updated RATIS-1625:
-----------------------------
Description:
As has been discussed in
[https://lists.apache.org/thread/tt1j3jkogh71k2hvq5gtltwmphxfy736]
, the problem is that:
* New nodes will be stopped by the leader because it's not in the old
configuration
* setConfiguration won't success because it cannot communicate to new nodes,
since they got shutdown.
Steps to repdoduce:
* Start a cluster with 3x nodes
* Start 2 new nodes with 5x configuration
* Call api to change the configuration in old nodes
Logs when calling admin api:
was:
As has been discussed in
[https://lists.apache.org/thread/tt1j3jkogh71k2hvq5gtltwmphxfy736]
, the problem is that:
* New nodes will be stopped by the leader because it's not in the old
configuration
*
> client.admin().setConfiguration fails due to ReconfigurationTimeoutException
> ----------------------------------------------------------------------------
>
> Key: RATIS-1625
> URL: https://issues.apache.org/jira/browse/RATIS-1625
> Project: Ratis
> Issue Type: Bug
> Reporter: Riguz Lee
> Priority: Major
>
> As has been discussed in
> [https://lists.apache.org/thread/tt1j3jkogh71k2hvq5gtltwmphxfy736]
> , the problem is that:
> * New nodes will be stopped by the leader because it's not in the old
> configuration
> * setConfiguration won't success because it cannot communicate to new nodes,
> since they got shutdown.
> Steps to repdoduce:
> * Start a cluster with 3x nodes
> * Start 2 new nodes with 5x configuration
> * Call api to change the configuration in old nodes
> Logs when calling admin api:
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
