Details
-
Bug
-
Resolution: Done
-
Major
-
14.0.0.CR1
-
None
-
None
Description
Originally reported on EAP: https://issues.redhat.com/browse/EAPSUP-961
In some cases, it seems Infinispan will try to follow-up an indexing operations by another.
The request to update indexes is added in thenCompose(), which means it's added as soon as the first operation is marked as complete, which actually happens in the index writer thread... which is precisely the thread responsible for consuming that queue.
That can lead to a deadlock: should the queue be full, the act of adding an element to that queue will block, which means the index writer thread, responsible for consuming that queue, will block, which means the queue will never get processed ever again.
The bug seems to have been introduced in ISPN-11731: https://github.com/infinispan/infinispan/commit/c68c255f3b81dfcb71a25051b38be94700ad5ef5
Attachments
Issue Links
- clones
-
JDG-5544 Potential deadlock in index writer threads under heavy load
- Closed