[jira] [Commented] (CASSANDRA-9954) Improve Java-UDF timeout detection

["Robert Stupp (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/CASSANDRA-9954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14651030#comment-14651030 ] 

Robert Stupp commented on CASSANDRA-9954:
-----------------------------------------

Cassci links (should appear soon):
[testall|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-9954-amok-udf-testall/]
[dtest|http://cassci.datastax.com/view/Dev/view/snazy/job/snazy-9954-amok-udf-dtest/]


> Improve Java-UDF timeout detection
> ----------------------------------
>
>                 Key: CASSANDRA-9954
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-9954
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Robert Stupp
>            Assignee: Robert Stupp
>             Fix For: 3.x
>
>
> CASSANDRA-9402 introduced a sandbox using a thread-pool to enforce security constraints and to detect "amok UDFs" - i.e. UDFs that essentially never return (e.g. {{while (true)}}.
> Currently the safest way to react on such an "amok UDF" is to _fail-fast_ - to stop the C* daemon since stopping a thread (in Java) is just no solution.
> CASSANDRA-9890 introduced further protection by inspecting the byte-code. The same mechanism can also be used to manipulate the Java-UDF byte-code.
> By manipulating the byte-code I mean to add regular "is-amok-UDF" checks in the compiled code.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)