Details
-
Story
-
Status: Resolved
-
Critical
-
Resolution: Won't Fix
-
None
-
None
-
None
Description
Occasional scheduler deadlock bugs would have benefited from proactive detection. Guava provides a utility class, CycleDetectingLockFactory, which is well-suited to this task.
Keeping with our general practice of leaving all assertions enabled at runtime unless data suggests performance is impacted, I propose replacing almost all usage of the synchronized keyword or a ReentrantReadWriteLock with a CycleDetectingLockFactory-managed variant unless we have data to suggest performance would be adversely impacted.
Attachments
Issue Links
- is related to
-
AURORA-801 deadlock in scheduler startup
- Resolved