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

Internal: Optimize#force() is not passed on to the shardrequest #7404

Closed
s1monw opened this Issue Aug 22, 2014 · 0 comments

Comments

Projects
None yet
1 participant
@s1monw
Copy link
Contributor

s1monw commented Aug 22, 2014

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.

@s1monw s1monw added bug labels Aug 22, 2014

s1monw added a commit to s1monw/elasticsearch that referenced this issue Aug 22, 2014

[ENGINE] Force optimize was not passed to shard request
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 s1monw closed this in #7405 Aug 22, 2014

s1monw added a commit that referenced this issue Aug 22, 2014

[ENGINE] Force optimize was not passed to shard request
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 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 s1monw added the v1.2.5 label Aug 22, 2014

s1monw added a commit that referenced this issue Aug 22, 2014

[ENGINE] Force optimize was not passed to shard request
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

[ENGINE] Force optimize was not passed to shard request
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 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

[ENGINE] Force optimize was not passed to shard request
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

[ENGINE] Force optimize was not passed to shard request
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

[ENGINE] Force optimize was not passed to shard request
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
You can’t perform that action at this time.