Misleading store state #1566
Labels
needs-type
Indicates an issue requires a type label.
status/discussion-wanted
The issue needs to be discussed.
Comments
rleungx
added a commit
to rleungx/pd
that referenced
this issue
Dec 1, 2021
close tikv#1566 Signed-off-by: Ryan Leung <rleungx@gmail.com>
ti-chi-bot
added a commit
that referenced
this issue
Mar 3, 2022
ref #1566 Signed-off-by: Ryan Leung <rleungx@gmail.com> Co-authored-by: Ti Chi Robot <ti-community-prow-bot@tidb.io>
|
Closed by #4687. |
|
The down/disconnect issue still exists, reopen it. |
|
There are no type labels on this issue. Please add an appropriate label by using the following command:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently, the status of down/disconnect is not reflected in the meta information of the store. As long as you do not manually go offline, the meta is always Up. This leads to the inability to determine the down state when using the grpc or HTTP interface to query the meta information of the store, and it is easy to mistake it as normal (but not).
Proposal: Define new state to use in the API, distinguish from that persistent to storage.
The text was updated successfully, but these errors were encountered: