Skip to content
New issue

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

Improve visibility of shard allocation issues #799

Open
Tracked by #1
hammerhead opened this issue Dec 12, 2022 · 0 comments
Open
Tracked by #1

Improve visibility of shard allocation issues #799

hammerhead opened this issue Dec 12, 2022 · 0 comments

Comments

@hammerhead
Copy link
Member

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants