You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Robert Stupp (JIRA)" <ji...@apache.org> on 2015/09/29 18:53:04 UTC
[jira] [Commented] (CASSANDRA-10395) Monitor UDFs using a single
thread
[ https://issues.apache.org/jira/browse/CASSANDRA-10395?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935430#comment-14935430 ]
Robert Stupp commented on CASSANDRA-10395:
------------------------------------------
Started working on this.
The benefit of this change is that we save UDF call latency caused by scheduling the UDF call.
The downside is that an endless-loop-UDF will really never return and thus not emit a warning to the client. CASSANDRA-9954 would bring back the warning for Java-UDFs.
/cc [~aweisberg] [~tjake]
> 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)