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
Internal: Optimize#force() is not passed on to the shardrequest #7404
Labels
Comments
s1monw
added a commit
to s1monw/elasticsearch
that referenced
this issue
Aug 22, 2014
The force flag to trigger optimiz calls of a single segment for upgrading etc. was never passed on to the shard request. Closes elastic#7404
s1monw
added a commit
that referenced
this issue
Aug 22, 2014
The force flag to trigger optimiz calls of a single segment for upgrading etc. was never passed on to the shard request. Closes #7404
s1monw
changed the title
Optimize#force() is not passed on to the shardrequest
[ENGINE] Optimize#force() is not passed on to the shardrequest
Aug 22, 2014
s1monw
added a commit
that referenced
this issue
Aug 22, 2014
The force flag to trigger optimiz calls of a single segment for upgrading etc. was never passed on to the shard request. Closes #7404
s1monw
added a commit
that referenced
this issue
Aug 22, 2014
The force flag to trigger optimiz calls of a single segment for upgrading etc. was never passed on to the shard request. Closes #7404
clintongormley
changed the title
[ENGINE] Optimize#force() is not passed on to the shardrequest
Internal: Optimize#force() is not passed on to the shardrequest
Sep 8, 2014
s1monw
added a commit
that referenced
this issue
Sep 8, 2014
The force flag to trigger optimiz calls of a single segment for upgrading etc. was never passed on to the shard request. Closes #7404
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
The force flag to trigger optimiz calls of a single segment for upgrading etc. was never passed on to the shard request. Closes elastic#7404
mute
pushed a commit
to mute/elasticsearch
that referenced
this issue
Jul 29, 2015
The force flag to trigger optimiz calls of a single segment for upgrading etc. was never passed on to the shard request. Closes elastic#7404
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
we have a force option to upgrade indices if there is even only a single segment. This setting is never passed on to the shardrequest.
The text was updated successfully, but these errors were encountered: