Failing tests 2016-08-02 [cassandra-3.9]

2016-08-02 Thread Joel Knighton
testall:
  All good! Nice work.

=

dtest:
  Rough day - 16 failures. All these failures are from problems creating a
connection to the CCM cluster under test. These failures are also happening
on the 2.2/3.0/3.9/trunk branches, so this is my highest priority to
resolve. I am yet to find the cause.

=

novnode_dtest
  17 failures. Same cause as the dtest failures above.

=

dtest_upgrade
  110 failures. Combination of the connection failures and the existing
upgrade test failures.

=

Today's email is brief because recapping 143 failures wouldn't do much
good. As soon as the connection issue is resolved, the emails will be back
to higher signal content.

Josh McKenzie should be back from vacation, so expect these emails to come
from him in the future.


C* data validation in new DC

2016-08-02 Thread Ashish Pandey
Hi All

We are running 2.0.14 and recently added new cassandra datacenter to the
existing datacenter. Wondering, if there is a recommended way in cassandra
to check data  completely sync'ed in new datacenter other than *nodetool
cfstats *which just gives estimate of number of keys

Thanks in advance
Ashish