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

Feature request: different timeout values by task_id #42

Closed
doingitbigdata opened this issue Sep 19, 2016 · 3 comments
Closed

Feature request: different timeout values by task_id #42

doingitbigdata opened this issue Sep 19, 2016 · 3 comments
Labels
enhancement v2.4.0

Comments

@doingitbigdata
Copy link

Currently the timeout parameter is global across multiple aggregrate tasks with different task_ids. I would like to request that this be changed such that different task_ids can have different timeout values.

Currently I have low volume tasks where I would like to set the timeout to a large number and conversely there are high volume tasks where I would like to set the timeout smaller to alleviate on memory usage.
fbaligand added a commit to fbaligand/logstash-filter-aggregate that referenced this issue Oct 15, 2016
@fbaligand
new feature: You can now define timeout options per task_id pattern
fbf716d 
(logstash-plugins#42)
fbaligand added a commit that referenced this issue Oct 15, 2016
@fbaligand
new feature: ability to define timeout options per task_id pattern (#42)
1580c55
@fbaligand
Copy link
Collaborator

Hi @doingitbigdata
I just released a new version which fixes your issue !
Hope you'll enjoy it !

@doingitbigdata
Copy link
Author

@fbaligand Great. Thanks!

@fbaligand
Copy link
Collaborator

Nice news that you enjoy it !
So I close the issue.

@fbaligand fbaligand mentioned this issue Nov 1, 2016
Merged
@azuk azuk mentioned this issue Apr 23, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement v2.4.0
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@doingitbigdata @fbaligand