Skip to content

BulkProcessor hangs instead of timeout #42528

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

Closed
lin-ye opened this issue May 24, 2019 · 6 comments
Closed

BulkProcessor hangs instead of timeout #42528

lin-ye opened this issue May 24, 2019 · 6 comments
Assignees
Labels
:Core/Infra/REST API REST infrastructure and utilities feedback_needed

Comments

@lin-ye
Copy link

lin-ye commented May 24, 2019

The problem described at https://discuss.elastic.co/t/bulkprocessor-hangs-instead-of-timeout/147737 doesn't seem resolved yet, and we got the same problem on the Java High Level Rest Client 6.5.4. Any plan on a fix for it?

@iverase iverase added the :Distributed Indexing/CRUD A catch all label for issues around indexing, updating and getting a doc by id. Not search. label May 24, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@ywelsch ywelsch added :Core/Infra/REST API REST infrastructure and utilities and removed :Distributed Indexing/CRUD A catch all label for issues around indexing, updating and getting a doc by id. Not search. labels May 24, 2019
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-core-infra

@zhaomoran
Copy link

I also encountered this problem in 6.3.1,I found this problem occurs when the cluster is busy.
BulkProcessor.builder(consumer, new BulkProcessor.Listener()) will occurs this problem.
BulkProcessor.builder(client, new BulkProcessor.Listener()) will throw RemoteTransportException、EsRejectedExecutionException

@henningandersen henningandersen self-assigned this Jul 9, 2019
@henningandersen
Copy link
Contributor

henningandersen commented Jul 9, 2019

@lin-ye and @zhaomoran , thanks for reporting this. Are you able to reproduce this in a standalone test case? If so, can you either share the code or describe what the test does?

I suspect you may have run into #36770, which is fixed in 6.6+. Is an upgrade to a newer version possible to see if this resolves the issue?

Following diagnostics info could also be helpful in diagnosing this (from when the problem has occurred):

  • hot threads
  • tasks

@astefan
Copy link
Contributor

astefan commented Aug 28, 2019

No further feedback received. @lin-ye @zhaomoran if you have the requested information please add it in a comment and we can look at re-opening this issue.

@astefan astefan closed this as completed Aug 28, 2019
@lin-ye
Copy link
Author

lin-ye commented Aug 28, 2019

@henningandersen Thanks for sharing the info. @astefan We haven't seen the issue anymore since upgrading to 6.8, so it might be fixed by #36770.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Core/Infra/REST API REST infrastructure and utilities feedback_needed
Projects
None yet
Development

No branches or pull requests

7 participants