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.

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 management #6914

Closed
clintongormley opened this issue Jul 18, 2014 · 24 comments
Closed

Task management #6914

clintongormley opened this issue Jul 18, 2014 · 24 comments
Assignees
Labels
:Distributed Coordination/Task Management Issues for anything around the Tasks API - both persistent and node level. >feature

Comments

@clintongormley
Copy link
Contributor

We need a task management API to allow management of long running tasks, like snapshot/restore, benchmarking, update-by-query etc.

The API should allow listing and aborting of ongoing tasks.

@1st
Copy link

1st commented Jul 18, 2014

+1. Waiting for this new feature!!!

@markharwood
Copy link
Contributor

Part of killing long running tasks will be tied up in this new generic timeout handling mechanism: #4586

@shikhar
Copy link
Contributor

shikhar commented Aug 5, 2014

Will this cover search requests? Since one can't know in advance very well if a search request will be long-running, I guess this task tracking would need to apply to all of them.

If this is not the plan, I think #7157 should be reopened.

@martijnvg
Copy link
Member

@shikhar The task infrastructure will be generic enough that it can be adopted in the search api as well.

@efuquen
Copy link

efuquen commented Aug 13, 2014

👍 Not having this has been a pain.

@shadow000fire
Copy link
Contributor

+1

2 similar comments
@ashvins
Copy link

ashvins commented Aug 28, 2014

+1

@JDvorak
Copy link

JDvorak commented Oct 28, 2014

👍

@sflint
Copy link

sflint commented Jan 12, 2015

+1

1 similar comment
@niemyjski
Copy link
Contributor

+1

@raf64flo
Copy link

Looking at it carefully. 👍

@smramdani
Copy link

+1
Would be a great feature as "running queries" and "long queries" in the classical RDBMSs.

@kennycason
Copy link

+1

@tostasqb
Copy link

+1

@kiryam
Copy link
Contributor

kiryam commented Apr 7, 2015

+1

1 similar comment
@chenryn
Copy link

chenryn commented Apr 8, 2015

+1

@kjelle
Copy link

kjelle commented Aug 19, 2015

+1

2 similar comments
@amontalenti
Copy link

+1

@BrickXu
Copy link

BrickXu commented Oct 21, 2015

+1

@imotov
Copy link
Contributor

imotov commented Nov 30, 2015

I created a new meta issue #15117 where work on the task management will be tracked. Closing this one.

@imotov imotov closed this as completed Nov 30, 2015
@garyelephant
Copy link

+1

@rfyiamcool
Copy link

thanks

@garyelephant
Copy link

Will this cover resource limit(similar with spark job executor's cpu,mem resource limit) using cgroups or something ? For Users who want to aggregate more than 1TB of index, it's likely to cause overall elasticsearch cluster overload, no response.

@imotov
Copy link
Contributor

imotov commented Apr 1, 2016

@garyelephant there are no immediate plans to do that as a part of task management effort. However, we are working on some improvements in this area. Please see the discussion in #11511.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Coordination/Task Management Issues for anything around the Tasks API - both persistent and node level. >feature
Projects
None yet
Development

No branches or pull requests