Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Multiple instances of the IO Manager could cause out of order IO storage. #35

Open
ikaneshiro opened this issue Feb 20, 2020 · 0 comments
Open

Multiple instances of the IO Manager could cause out of order IO storage. #35

ikaneshiro opened this issue Feb 20, 2020 · 0 comments

Comments

@ikaneshiro
Copy link
Contributor

Capturing Dialogue from: #34 (comment)

Currently the IO Manager will independently handles each message containing a chunk of job output and appends it to redis. This leaves a race wrt the order of output between the handler and redis in the case of multiple IO Managers running at the same time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@ikaneshiro