[CURATOR-233] Bug in double barrier

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 2.8.0
• Component/s: Recipes
• Assignee: Mike Drob
• Reporter: J D
• Created: 11/Jul/15 21:41
• Updated: 17/Jul/22 06:35
• Resolved: 17/Jul/22 06:35

Description

Hi,

I think I discovered a bug in the internalLeave method of the double barrier implementation.

When a client is told to leave the barrier after maxWait it does not do so. A flag is set but the client does not leave the barrier, instead it keeps iterating through the control loop and drives CPU usage to 100%.

I have attached an example.

Best regards

Lianro

Issue Links

• duplicates: CURATOR-536 Infinite loop instead of timeout on DistributedDoubleBarrier::internalLeave
• links to: GitHub Pull Request #207