Open xinhaoz opened 3 days ago
Describe the problem
The DB pages should not fail on any one query failure. In #118904, we erroneously started reading rows unconditionally from the SHOW RANGES response, which leads to a page crash. https://github.com/cockroachdb/cockroach/blob/18a2af14d9690f433ce47e00a09e3090687b801d/pkg/ui/workspaces/cluster-ui/src/api/databaseDetailsApi.ts#L385
rows
SHOW RANGES
These queries can't show partial results so we should just exit on returned errors.
To Reproduce This can be seen in clusters with an unavailable replica, as the query fetching store ids via SHOW RANGES will fail.
Epic CRDB-37558
Hi @xinhaoz, please add branch-* labels to identify which branch(es) this C-bug affects.
:owl: Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.
Describe the problem
The DB pages should not fail on any one query failure. In #118904, we erroneously started reading
rows
unconditionally from theSHOW RANGES
response, which leads to a page crash. https://github.com/cockroachdb/cockroach/blob/18a2af14d9690f433ce47e00a09e3090687b801d/pkg/ui/workspaces/cluster-ui/src/api/databaseDetailsApi.ts#L385These queries can't show partial results so we should just exit on returned errors.
To Reproduce This can be seen in clusters with an unavailable replica, as the query fetching store ids via
SHOW RANGES
will fail.Epic CRDB-37558