cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joshua McKenzie (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-9897) Windows dtest: failures
Date Tue, 28 Jul 2015 19:45:04 GMT


Joshua McKenzie commented on CASSANDRA-9897:

Hm. Looks like the problem's not that our subprocess is blocking when it has a valid return,
but that nodetool isn't getting a return from the node *when the ccm cluster is run from within
the dtest*. An attempt to perform the same nodetool -h localhost -p 7100 flush from cassandra\bin
also hangs indefinitely, yet flat C* runs and straight ccm runs w/the same compiled .jars
work fine. Other nodetool commands seem to work against the dtest cluster without issue and
the logs on the node indicate that it got, and completed, the flush.

> Windows dtest: failures
> ----------------------------------------
>                 Key: CASSANDRA-9897
>                 URL:
>             Project: Cassandra
>          Issue Type: Sub-task
>            Reporter: Joshua McKenzie
>            Assignee: Joshua McKenzie
>              Labels: Windows
>             Fix For: 2.2.1
> System call is linux-specific:
> {noformat}
> ERROR [CommitLogArchiver:1] 2015-07-24 13:26:39,622 - Exception
in thread Thread[CommitLogArchiver:1,5,main]
> java.lang.RuntimeException: Exception while executing the command:
cp c:\temp\dtest-phi4wd\test\node1\commitlogs\CommitLog-5-1437758795056.log c:  emp     mpkzsvkb/CommitLog-5-1437758795056.log,
command error Code: 1, command output: cp: accessing `c:\temp\tmpkzsvkb/CommitLog-5-1437758795056.log':
Invalid argument
>         at ~[guava-16.0.jar:na]
>         at ~[main/:na]
>         at java.util.concurrent.Executors$ ~[na:1.8.0_45]
>         at ~[na:1.8.0_45]
>         at java.util.concurrent.ThreadPoolExecutor.runWorker(
>         at java.util.concurrent.ThreadPoolExecutor$
>         at [na:1.8.0_45]
> {noformat}

This message was sent by Atlassian JIRA

View raw message