Misleading store state

Open disksing opened this issue 6 years ago • 3 comments

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.

Jun 05 '19 11:06 disksing

Closed by #4687.

Apr 01 '22 08:04 rleungx

The down/disconnect issue still exists, reopen it.

Jan 07 '25 04:01 rleungx

There are no type labels on this issue. Please add an appropriate label by using the following command:

/type <type-name>

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.

Jan 07 '25 04:01 ti-chi-bot[bot]