You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Doug Rohrer (Jira)" <ji...@apache.org> on 2024/01/10 17:47:00 UTC

[jira] [Commented] (CASSANDRA-19212) Better handle Spark job timeouts/process killing in Analytics tests

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

Doug Rohrer commented on CASSANDRA-19212:
-----------------------------------------

Closed the PR for now as another change removed the running of Spark in a separate process. We may revisit that later though, so I'll keep the branch around.

> Better handle Spark job timeouts/process killing in Analytics tests
> -------------------------------------------------------------------
>
>                 Key: CASSANDRA-19212
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19212
>             Project: Cassandra
>          Issue Type: Bug
>          Components: Analytics Library
>            Reporter: Doug Rohrer
>            Assignee: Doug Rohrer
>            Priority: Normal
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> The Process#destroyForcibly() call in ResiliencyTestBase#bulkWriteData can complete without the process actually exiting (and is documented to do so). We should wait on the process to exit before attempting to read the exit code, which throws if the process hasn’t yet exited.  Otherwise, we can lose the Spark output when the test determines that the job is taking too long.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org