[
https://issues.apache.org/jira/browse/CASSANDRA-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15050005#comment-15050005
]
Robert Stupp commented on CASSANDRA-10395:
------------------------------------------
Looked at it. Some of the things you addressed feel a too intrusive for 3.0.x
(e.g. using the "optimal" timeout detection). So I'm currently thinking of
resolving this as "won't fix" if we can live with the current state and fix it
properly in CASSANDRA--9954 for 3.x. WDYT?
> Monitor UDFs using a single thread
> ----------------------------------
>
> Key: CASSANDRA-10395
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10395
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Robert Stupp
> Assignee: Robert Stupp
> Priority: Minor
> Fix For: 3.0.x
>
>
> Actually each UDF execution is handed over to a separate thread pool to be
> able to detect UDF timeouts. We could actually leave UDF execution in the
> "original" thread but have another thread/scheduled job regularly looking for
> UDF timeouts, which would save some time executing the UDF.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
