Conversation
Signed-off-by: Slach <[email protected]>
…omething wrong with tearDown.sh, wrong NuRaft quorum state after replicas: 0 -> replicas: 3) Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
…(23.8) Signed-off-by: Slach <[email protected]>
|
Wait when resolve ClickHouse/ClickHouse#53481 and ClickHouse/ClickHouse#54129 |
|
does this fix the issue where |
|
@bputt-e in the new approach, we are trying to use command |
…ouse#54129, test_keeper_rescale passed, but quorum lost after 2 hour Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
Signed-off-by: Slach <[email protected]>
Depends on ClickHouse/ClickHouse#53481
This will help a lot for maintainers to adopt your Pull Request.
Important items to consider before making a Pull Request
Please check items PR complies to:
next-releasebranch, not intomasterbranch1. More info--
1 If you feel your PR does not affect any Go-code or any testable functionality (for example, PR contains docs only or supplementary materials), PR can be made into
masterbranch, but it has to be confirmed by project's maintainer.