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

Force optimize was not passed to shard request #7405

Merged
merged 1 commit into from Aug 22, 2014

Conversation

Projects
None yet
3 participants
@s1monw
Copy link
Contributor

commented 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 s1monw added the review label Aug 22, 2014

@jpountz

This comment has been minimized.

Copy link
Contributor

commented Aug 22, 2014

LGTM thanks!

[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 force-pushed the s1monw:issues/7404 branch to fdf1998 Aug 22, 2014

@s1monw s1monw merged commit fdf1998 into elastic:master Aug 22, 2014

@s1monw s1monw removed the review label Aug 22, 2014

@s1monw s1monw deleted the s1monw:issues/7404 branch Aug 22, 2014

@clintongormley clintongormley changed the title [ENGINE] Force optimize was not passed to shard request Internal: Force optimize was not passed to shard request Sep 8, 2014

@clintongormley clintongormley changed the title Internal: Force optimize was not passed to shard request Force optimize was not passed to shard request Jun 7, 2015

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.