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

Job control (abort) mechanism #9

Open
CaptainCodeman opened this issue Jul 9, 2016 · 0 comments
Open

Job control (abort) mechanism #9

CaptainCodeman opened this issue Jul 9, 2016 · 0 comments

Comments

@CaptainCodeman
Copy link
Owner

Check on task start as part of lock: return error but with http OK status to abort any task retry
Would allow processing to halt and tasks to quickly drain
CaptainCodeman added a commit that referenced this issue Jul 11, 2016
@CaptainCodeman
Refactor
ef6d680 
Include job type in key names. Closes #1
Record task start + end times, processing time and wall-time. Closes #2
Rollup counter and timers into parent (shard -> namespace, namespace -> job). Closes #3
Rename iterator / splitter. Closes #5
Record job data and use to track overall status when shard / namespaces complete. Closes #6
Use transactional task enqueueing rather than named tasks #7
Provide abort mechanism (no write yet) #9
Output to cloud storage and rollup files (slice -> shard, shard -> namespace) Closes #12
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
@CaptainCodeman