-
Notifications
You must be signed in to change notification settings - Fork 76
Orchestrator: Fixes Workers #691
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
…ra into fix/multiple-minors
Mohiiit
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can you clarify the difference between context implementation and the trigger implementation here? I see it's been used interchangeably or maybe I am missing something and do we really need that segregation?
Co-authored-by: Mohit Dhattarwal <[email protected]>
Trantorian1
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
From my limited experience with orchestrator, lgtm 👌
orchestrator/src/worker/event_handler/triggers/data_submission.rs
Outdated
Show resolved
Hide resolved
| pub struct ProcessingContext { | ||
| pub config: Arc<Config>, | ||
| pub earliest_failed_block: Option<u64>, | ||
| } |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duplicate struct?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
madara/orchestrator/src/worker/event_handler/triggers/data_submission.rs
Lines 161 to 164 in 1e2a427
| struct ProcessingContext { | |
| config: Arc<Config>, | |
| earliest_failed_block: Option<u64>, | |
| } |
Co-authored-by: Trantorian1 <[email protected]>
Co-authored-by: Trantorian1 <[email protected]>
Resolves #590: Optimize Orchestrator Chain Settlement Logic
Problem
The Orchestrator currently halts the entire chain settlement process when any job reaches
FailedorVerification Timeoutstatus, leading to inefficient processing and unnecessary blocking of independent operations.Current problematic behavior:
StateTransitionfor block 5 is halted whenSnosRunfor block 10 fails)Solution
This PR optimizes the worker logic to continue processing independent jobs even when unrelated jobs fail, improving overall system resilience and throughput.