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

Add `force-recover` corrupted shards command to reroute #8708

Closed
s1monw opened this issue Nov 29, 2014 · 12 comments

Comments

@s1monw
Copy link
Contributor

commented Nov 29, 2014

we give advice to rm shards on the FS if they got corrupted like here #8707 I personally think we should have an endpoint to force recovery for these shards to make it easier for users.

@clintongormley

This comment has been minimized.

Copy link
Member

commented Dec 1, 2014

+1

@clintongormley clintongormley added help wanted and removed discuss labels Dec 1, 2014

@JamieCressey

This comment has been minimized.

Copy link

commented Mar 4, 2015

+1

@s1monw s1monw added v1.6.0 and removed v1.5.0 labels Mar 17, 2015

@nabheet

This comment has been minimized.

Copy link

commented Apr 1, 2015

+1

3 similar comments
@nick4eva

This comment has been minimized.

Copy link

commented Apr 8, 2015

+1

@Bertg

This comment has been minimized.

Copy link

commented Apr 9, 2015

👍

@erikringsmuth

This comment has been minimized.

Copy link
Contributor

commented Apr 29, 2015

👍

@phreakinggeek

This comment has been minimized.

Copy link

commented May 19, 2015

👍 👍

@ishare

This comment has been minimized.

Copy link
Contributor

commented Jun 7, 2015

does it mean propose to be added to v2.0.0 ?

@pataditya

This comment has been minimized.

Copy link

commented Aug 18, 2015

+1

@s1monw

This comment has been minimized.

Copy link
Contributor Author

commented Aug 18, 2015

I think we can close this @bleskes since we now allocate them fresh on the corrupted node from the primary?

@bleskes

This comment has been minimized.

Copy link
Member

commented Aug 18, 2015

+1 to close this. A corrupted shard should be replaced with a fresh copy now.

@phreakinggeek

This comment has been minimized.

Copy link

commented Nov 17, 2015

Is that true for single node ES instances as well?

@clintongormley clintongormley added v2.2.0 and removed v2.1.0 labels Nov 20, 2015

@clintongormley clintongormley removed the v2.2.0 label Jan 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
You can’t perform that action at this time.