Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

Potential deadlock with balanced splitters and ,UPDATE combinations

Description

If OUTPUT/BUILD,UPDATE's were downstream from a balanced splitter, the query could deadlock.
A suppressed UPDATE sink is never initialized and therefore the arm of the splitter is not started or stopped. In that case the other outputs to the splitter are pulled until the balanced splitter buffer is full and the query deadlocks.

In the case of unbalanced splitters (which spill if being pull unevenly), the suppressed UPDATE sink, would cause the splitter input to never be stopped, which could cause other problems.

Conclusion

None

Activity

Show:

Jacob Cobbett-Smith March 14, 2018 at 7:13 PM

On older builds, one workaround is to use #option('splitterSpill', 1) in jobs that are effected.

Fixed
Pinned fields
Click on the next to a field label to start pinning.

Details

Components

Assignee

Reporter

Priority

Fix versions

Pull Request URL

https://github.com/hpcc-systems/HPCC-Platform/pull/9916

Created April 21, 2017 at 5:26 PM
Updated March 14, 2018 at 7:13 PM
Resolved May 3, 2017 at 2:37 PM