[
https://issues.apache.org/jira/browse/CASSANDRA-19212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Doug Rohrer updated CASSANDRA-19212:
------------------------------------
Resolution: Abandoned
Status: Resolved (was: Open)
No longer spinning up a separate process for Spark, so we don't need this work
any more.
> 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-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
