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

Cluster Health API: Add initializing_shards and unassigned_shards to the response #330

Closed
kimchy opened this issue Aug 21, 2010 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Aug 21, 2010

Add the number of initializing shards (possible being recovered) and unassigned shards (shards that are not assigned to any node) to the response (on all levels).

@kimchy
Copy link
Member Author

kimchy commented Aug 21, 2010

Cluster Health API: Add initializing_shards and unassigned_shards to the response, closed by 38e6649.

williamrandolph pushed a commit to williamrandolph/elasticsearch that referenced this issue Jun 4, 2020
In Hadoop-like envs, Progressable might be invalid causing exceptions
when going through the MR layer.

Fix elastic#330
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
…lastic#330)

Fixed typo and cleanup for ems settings in test2.tfvar file

* Fixed typo and cleanup for ems settings in test2.tfvar file


Approved-by: Can Yildiz
costin added a commit that referenced this issue Dec 6, 2022
🤖 ESQL: Merge upstream
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
Remove oss leftovers (used for the release license defaults) after elastic#323 and adjust tests.
Also fix pip3 dependency resolver to match the changes in elastic/rally#1088.
emilykmarx pushed a commit to emilykmarx/elasticsearch that referenced this issue Dec 26, 2023
Remove refactor notice. Remove deprecated Jenkins build badge in favor of travis

Fixes elastic#330
This issue was closed.
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

1 participant