Never mind, it has been fixed in recent release and I realized I was using the
wrong ML for that subject
> On Aug 28, 2015, at 18:49, Cyril Scetbon <cyril.scet...@free.fr> wrote:
>
> Hi guys,
>
> I got some issues with ccm and unit tests in java-driver. Here is what I see :
>
> tail -f /tmp/1440780247703-0/test/node5/logs/system.log
> INFO [STREAM-IN-/127.0.1.3] 2015-08-28 16:45:06,009 StreamResultFuture.java
> (line 220) [Stream #22d9e9f0-4da4-11e5-9409-5d8a0f12fefd] All sessions
> completed
> INFO [main] 2015-08-28 16:45:06,009 StorageService.java (line 1014) Bootstrap
> completed! for the tokens [8907077543698545973]
> INFO [main] 2015-08-28 16:45:06,010 ColumnFamilyStore.java (line 785)
> Enqueuing flush of Memtable-local@1738175520(84/840 serialized/live bytes, 8
> ops)
> INFO [FlushWriter:1] 2015-08-28 16:45:06,013 Memtable.java (line 331) Writing
> Memtable-local@1738175520(84/840 serialized/live bytes, 8 ops)
> INFO [FlushWriter:1] 2015-08-28 16:45:06,072 Memtable.java (line 371)
> Completed flushing
> /tmp/1440780247703-0/test/node5/data/system/local/system-local-jb-6-Data.db
> (117 bytes) for commitlog position ReplayPosition(segmentId=1440780271059,
> position=143914)
> INFO [main] 2015-08-28 16:45:06,074 ColumnFamilyStore.java (line 785)
> Enqueuing flush of Memtable-local@1171696270(50/500 serialized/live bytes, 4
> ops)
> INFO [FlushWriter:1] 2015-08-28 16:45:06,074 Memtable.java (line 331) Writing
> Memtable-local@1171696270(50/500 serialized/live bytes, 4 ops)
> INFO [FlushWriter:1] 2015-08-28 16:45:06,118 Memtable.java (line 371)
> Completed flushing
> /tmp/1440780247703-0/test/node5/data/system/local/system-local-jb-7-Data.db
> (97 bytes) for commitlog position ReplayPosition(segmentId=1440780271059,
> position=144080)
> INFO [main] 2015-08-28 16:45:06,122 StorageService.java (line 1499) Node
> /127.0.1.5 state jump to normal
> INFO [main] 2015-08-28 16:45:06,124 CassandraDaemon.java (line 518) Waiting
> for gossip to settle before accepting client requests...
> INFO [main] 2015-08-28 16:45:14,125 CassandraDaemon.java (line 550) No gossip
> backlog; proceeding
> INFO [main] 2015-08-28 16:45:14,187 Server.java (line 155) Starting listening
> for CQL clients on /127.0.1.5:9042...
> INFO [main] 2015-08-28 16:45:14,224 ThriftServer.java (line 99) Using
> TFramedTransport with a max frame size of 15728640 bytes.
> INFO [main] 2015-08-28 16:45:14,225 ThriftServer.java (line 118) Binding
> thrift service to /127.0.1.5:9160
> INFO [main] 2015-08-28 16:45:14,233 TServerCustomFactory.java (line 47) Using
> synchronous/threadpool thrift server on 127.0.1.5 : 9160
> INFO [Thread-10] 2015-08-28 16:45:14,233 ThriftServer.java (line 135)
> Listening for thrift clients...
>
>
> However ccm doesn't see that node5 is running and listening :
>
> 0 [Scheduled Tasks-0] INFO com.datastax.driver.core.Cluster - New
> Cassandra host /127.0.1.5:9042 added
> 53833 [main] INFO com.datastax.driver.core.TestUtils - 127.0.1.5 is not
> UP after 60s
> 69528 [main] INFO com.datastax.driver.core.CCMBridge - Error during
> tests, kept C* logs in /tmp/1440780247703-0
>
> But at the same time I can see that node5 is running and I can also connect
> to it :
>
> # netstat -lnt|grep 9042
> tcp 0 0 127.0.1.5:9042 0.0.0.0:* LISTEN
> tcp 0 0 127.0.1.3:9042 0.0.0.0:* LISTEN
> tcp 0 0 127.0.1.4:9042 0.0.0.0:* LISTEN
> tcp 0 0 127.0.1.2:9042 0.0.0.0:* LISTEN
> tcp 0 0 127.0.1.1:9042 0.0.0.0:* LISTEN
> root@ip-10-0-1-97:~# nc 127.0.1.5 9042
>
> After the error then ccm turns all nodes down to end unit tests :
>
> INFO [GossipStage:1] 2015-08-28 16:45:31,864 Gossiper.java (line 863)
> InetAddress /127.0.1.1 is now DOWN
> INFO [GossipStage:1] 2015-08-28 16:45:34,989 Gossiper.java (line 863)
> InetAddress /127.0.1.3 is now DOWN
> INFO [GossipStage:1] 2015-08-28 16:45:38,087 Gossiper.java (line 863)
> InetAddress /127.0.1.2 is now DOWN
> INFO [StorageServiceShutdownHook] 2015-08-28 16:45:39,181 ThriftServer.java
> (line 141) Stop listening to thrift clients
> INFO [StorageServiceShutdownHook] 2015-08-28 16:45:39,200 Server.java (line
> 181) Stop listening for CQL clients
>
> Any idea ? Any known issue ?
