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
TASK: Execution delay is not respected for the jobs #409
Comments
alirezazamani
pushed a commit
to alirezazamani/helix
that referenced
this issue
Aug 15, 2019
In the Task Framework part of helix, execution delay for the jobs is not respected. In this commit, when the job is extracted from the inflighJobs queue, the timeline has been checked before scheduling. This commit fixes issue apache#409.
alirezazamani
pushed a commit
to alirezazamani/helix
that referenced
this issue
Aug 19, 2019
In the Task Framework part of helix, execution delay for the jobs is not respected. In this commit, when the job is extracted from the inflighJobs queue, the timeline has been checked before scheduling. This commit fixes issue apache#409.
alirezazamani
pushed a commit
to alirezazamani/helix
that referenced
this issue
Aug 19, 2019
In the Task Framework part of helix, execution delay for the jobs is not respected. In this commit, when the job is extracted from the inflighJobs queue, the timeline has been checked before scheduling. This commit fixes issue apache#409.
alirezazamani
pushed a commit
to alirezazamani/helix
that referenced
this issue
Aug 20, 2019
In the Task Framework part of helix, execution delay for the jobs is not respected. In this commit, when the job is extracted from the inflighJobs queue, the timeline has been checked before scheduling. This commit fixes issue apache#409.
alirezazamani
pushed a commit
to alirezazamani/helix
that referenced
this issue
Aug 20, 2019
In the Task Framework part of helix, execution delay for the jobs is not respected. In this commit, when the job is extracted from the inflighJobs queue, the timeline has been checked before scheduling. This commit fixes issue apache#409.
It is fixed in PR #410. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current implementation of Task Framework checks if a Job is ready for the scheduling or not. If not, the job is inserted in the inflight jobs without any delay time restrictions which is not desirable.
The text was updated successfully, but these errors were encountered: