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.

Sign up for GitHub

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

Jump to bottom

Optimize API: Don't execute concurrent optimize operations (shard level) on the same node #846

Closed
kimchy opened this issue Apr 10, 2011 · 0 comments
Closed

Optimize API: Don't execute concurrent optimize operations (shard level) on the same node #846

kimchy opened this issue Apr 10, 2011 · 0 comments
Labels
>enhancement v0.16.0

Comments

@kimchy
Copy link
Member

kimchy commented Apr 10, 2011

Optimize API: Don't execute concurrent optimize operations (shard level) on the same node in order to reduce the IO overload of a single optimize request.
@kimchy kimchy closed this as completed in decb5fa Apr 10, 2011
mindw pushed a commit to mindw/elasticsearch that referenced this issue Sep 5, 2022
Merged in dev/can/dev3-disk-increase-2022-08-24 (pull request elastic…
9d30d9d 
…#846)

Increase dev3 engageli disk space


Approved-by: Maxime Tremblay
Approved-by: Gabi Davar
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
>enhancement v0.16.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@kimchy