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

Setting index/bulk thread pools with queue_size can cause replica shard failures #3526

Closed
kimchy opened this issue Aug 17, 2013 · 1 comment

Comments

@kimchy
Copy link
Member

kimchy commented Aug 17, 2013

When setting queue_size on the index/bulk thread pools, they can cause replica shard failures when a request ends up being rejected on the replica shard. We should not adhere to the queue_size limit when executing the operation on the replica (which is perfectly fine, since the primary shard will make sure to limit it).

@s1monw
Copy link
Contributor

s1monw commented Aug 17, 2013

+1

@ghost ghost assigned kimchy Aug 17, 2013
kimchy added a commit to kimchy/elasticsearch that referenced this issue Aug 23, 2013
@kimchy kimchy closed this as completed in 86c95ab Aug 23, 2013
kimchy added a commit that referenced this issue Aug 23, 2013
kimchy added a commit that referenced this issue Oct 17, 2013
…n executed over network

The #3526 fix was not complete, it handled cases of on node execution, but didn't properly handle cases where it was executed over the network, and forcing the execution of the replica operation when done over the wire.

This relates to #3854

closes #3929
kimchy added a commit that referenced this issue Oct 17, 2013
…n executed over network

The #3526 fix was not complete, it handled cases of on node execution, but didn't properly handle cases where it was executed over the network, and forcing the execution of the replica operation when done over the wire.

This relates to #3854

closes #3929
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
mute pushed a commit to mute/elasticsearch that referenced this issue Jul 29, 2015
…n executed over network

The elastic#3526 fix was not complete, it handled cases of on node execution, but didn't properly handle cases where it was executed over the network, and forcing the execution of the replica operation when done over the wire.

This relates to elastic#3854

closes elastic#3929
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants