[
https://issues.apache.org/jira/browse/BLUR-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14078338#comment-14078338
]
Garrett Barton commented on BLUR-350:
-------------------------------------
I'm interested in picking this one up, couple questions:
Are you picturing another method say getTimeoutMS() that's overridable on the
command interface? Or as an additional parameter passed in to execute()?
Is the existing cancellation code what I see in the StopExecutionCollector? Is
that where you would expect it to continue to live or more like that paradigm
moving into the command itself?
Is the cancellation timeout per shard hit or total across its time within the
shard server? Should that be configurable?
> Execution interruption
> ----------------------
>
> Key: BLUR-350
> URL: https://issues.apache.org/jira/browse/BLUR-350
> Project: Apache Blur
> Issue Type: Sub-task
> Components: Blur
> Affects Versions: 0.2.4
> Reporter: Aaron McCurry
>
> Execution interruption is needed in the new command feature in Blur platform
> similar to query timeout and/or query cancellation.
> - This feature should allow the running command to be interrupted via an
> external caller.
> - This feature should allow the running command to be interrupted via timeout
> provided on the command itself.
> - Anytime a GC back pressure event is triggered all currently commands should
> be interrupted.
> All of these features are currently implemented for the query call in Blur
> today so most of this feature is porting that behavior over to run in the
> command call.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
