BatchExecutor sometimes forgets to schedule the processor since HSEARCH-3084

Description

The problem occurs randomly, but fairly frequently; see for example https://ci.hibernate.org/blue/organizations/jenkins/hibernate-search/detail/master/464/pipeline/85

It seems related to how we schedule the next runnable in the executor.

Activity

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Priority

Created October 9, 2019 at 7:09 AM
Updated October 25, 2019 at 3:07 PM
Resolved October 10, 2019 at 6:49 AM