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

Client need to receive a JOB_CREATED from server before submitting a new job #77

Open
No-ops opened this issue Mar 2, 2017 · 1 comment
Open

Client need to receive a JOB_CREATED from server before submitting a new job #77

No-ops opened this issue Mar 2, 2017 · 1 comment

Comments

@No-ops
Copy link
Collaborator

No-ops commented Mar 2, 2017

We are currently locking in client.do() to avoid a race condition when submitting jobs. We do not have anything to identify the submitted job with when receiving a JOB_CREATED response from the server so multiple simultaneous job submissions need to happen on separate connections if we don't want to lock.

Previous discussion on this can be found in #75

Protocol reference: http://gearman.org/protocol/
@No-ops No-ops mentioned this issue Mar 2, 2017
Merged
@tamalsaha
Copy link
Collaborator

/cc: @ashiquzzaman33, @sadlil

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
2 participants
@tamalsaha @No-ops