[GOBBLIN-2037] Start DagActionMonitor functionality after its Dependencies

• Type: Bug
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Component/s: gobblin-service
• Assignee: Abhishek Tiwari
• Reporter: Urmi Mustafi
• Created: 05/Apr/24 21:03
• Updated: 05/Apr/24 22:11

Description

The DagActionStoreChangeMonitor cannot be started before the Flowgraph, DagManager, and SpecCompiler are up and running. When the monitor is initialized by Guice, it was previously also starting to load dagActions from the store immediately to compile and process. There is a race condition created where the actions can be loaded too quickly from the store and passed to the specCompiler before it's ready. The SpecCompiler hangs waiting for the flowGraph to load, causing startup to fail. 

The solution is the bind the monitor in Guice but only enable processing of actions after the GobblinServiceManager ensures other classes are ready to be called by the DagActionStoreChangeMonitor.