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

Andrei Sereda commented on CALCITE-2442:
----------------------------------------

{quote}
Can someone please clarify: is this "cassandra mini cluster" a separate o/s 
process?
{quote}

It is using [CassandraUnit|https://github.com/jsevellec/cassandra-unit] which 
starts embedded version of cassandra using [Cluster 
API|https://docs.datastax.com/en/drivers/java/3.0/com/datastax/driver/core/Cluster.html]
 (not a sub-process with  
[ProcessBuilder|https://docs.oracle.com/javase/7/docs/api/java/lang/ProcessBuilder.html])
 JVM shutdown should  stop any running instances.

To check the pid run the following (same user as cassandra daemon): 
{code:bash}
$ netstat -nlp | grep :9142
OR
$ /usr/sbin/lsof -i -P -n | grep 9142
{code}

The reason we added explicit shutdown is because of temporary folders. Also 
being able to close cassandra cluster more gracefully (it is possible cluster 
uses shutdown hook).


> Cassandra unit test leaves stale folders in cassandra/ module on Windows
> ------------------------------------------------------------------------
>
>                 Key: CALCITE-2442
>                 URL: https://issues.apache.org/jira/browse/CALCITE-2442
>             Project: Calcite
>          Issue Type: Bug
>          Components: cassandra
>            Reporter: Andrei Sereda
>            Priority: Major
>
> [~Sergey Nuyanzin] reported that 
> [CassandraUnit|https://github.com/jsevellec/cassandra-unit] leaves 
> {{.toDelete}} folder in maven module folder ({{cassandra/}}) rather than 
> {{target/}} where all build and temporary files should be located.
> {quote}
> There is one more strange thing (at least on Windows): while building a
> file with name ".toDelete" is generated under calcite\cassandra and it's
> not removed by the end of tests
> Is there a way to make cassandra generates these files in target directory
> e.g.?
> {quote}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to