We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
when verify client version, if the meta leader change, and then cannot write version key in metad.
verify client version
(root@nebula) [(none)]> show hosts +-----------------+------+----------+--------------+----------------------+------------------------+----------+ | Host | Port | Status | Leader count | Leader distribution | Partition distribution | Version | +-----------------+------+----------+--------------+----------------------+------------------------+----------+ | "192.168.15.13" | 3772 | "ONLINE" | 16 | "sf1:9, sf100:7" | "sf1:24, sf100:24" | "v3.0.0" | | "192.168.15.13" | 2772 | "ONLINE" | 32 | "sf1:15, sf100:17" | "sf1:24, sf100:24" | "v3.0.0" | | "192.168.15.13" | 1772 | "ONLINE" | 0 | "No valid partition" | "sf1:24, sf100:24" | | +-----------------+------+----------+--------------+----------------------+------------------------+----------+ Got 3 rows (time spent 2872/4624 us) Mon, 07 Feb 2022 07:30:19 UTC
steps:
for i in `seq 1 3`;do ./nebula$i/scripts/nebula.service start all;done
The text was updated successfully, but these errors were encountered:
Thanks, we should verify the result of doSyncPut.
Sorry, something went wrong.
zhaohaifei
No branches or pull requests
when
verify client version
, if the meta leader change, and then cannot write version key in metad.steps:
The text was updated successfully, but these errors were encountered: