ATLAS-5093: Ensure executors are available and alive before submitting import tasks - #429
Merged
Merged
Conversation
jackhalfalltrades
force-pushed
the
ATLAS-5093
branch
from
August 20, 2025 22:56
d3101dc to
8c4b478
Compare
DishaTalreja3
approved these changes
Aug 20, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changes were proposed in this pull request?
The changes are to ensure if the executors are alive before submitting a import task, with additional unit test coverage proving the executors are not available on passive instances and at any point in time with concurrency only one executor is created.
How was this patch tested?
Deployed this code in a YCloud cluster and ran multiple replication policies to test the atlas Async Import Process.