crate / crate/crate-admin

Improve visibility of shard allocation issues

Open
#799 0 comments 0 reactions 0 assignees View on GitHub
complexity: no estimate contributions welcome feature feature: shards
Dominant language
JavaScript
Stars
27
Forks
18
PR merge metrics
No merged PRs in 30d

Description

In situations when shards cannot be allocated and a table/partition shows a yellow/red state, it is difficult for users to troubleshoot the reason with information shown in the Admin UI.

To give a simple example, create this table: `CREATE TABLE t (a INTEGER) WITH ("routing.allocation.require.name" = 'abc');`. The allocation requirement cannot be fulfilled, so the table health shows as red in the Admin UI. However, the user cannot find out through the Admin UI what the actual issue is:
* The table overview says "Health: red", but provides no further reasoning
* In the "Shards" tab, the table/shards don't show

Only when querying `sys.allocations` manually, and looking at the `decisions`/`explanation` columns, the root cause becomes visible.

**Suggested improvement**: Make information from `sys.allocations` more visible in the Admin UI, so users can troubleshoot allocation issues on their own, without having to know about additional `sys` tables.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.