Failing tests 2016-08-03 [cassandra-3.9]
Summary: Somewhat messy day, but I believe things should look less noisy tomorrow so we can get a better view of what we have left to a stable board. Going to try a slightly new format: [Failures] testall: 1 dtest: 0 novnode_dtest: 17 upgrade: 110 [Details] testall (1): CommitLogSegmentManagerTest.testCompressedCommitLogBackpressure CASSANDRA-12283, currently assigned to blerer novnode_dtest (17): Bulk: Hard to separate signal from noise due to rampant timeouts and nodes being marked down. This is possibly due to a problem in the python driver that was tracked down today - Joel, can you confirm? An example message: ('Unable to complete the operation against any hosts', {: ConnectionException('Host has been marked down or removed',), : ConnectionException('Host has been marked down or removed',), : ConnectionException('Host has been marked down or removed',)}) cql_tests.MiscellaneousCQLTester.prepared_statement_invalidation_test **Needs Triage** New failure as of yesterday, tracked by CASSANDRA-12361 materialized_views_test.TestMaterializedViews.complex_repair_test Assigned to cyeksigian Intermittent failure Last comment from Philip indicates we want to move this to dtest_large. Pinged Jim. upgrade (110): CASSANDRA-12236 was committed today so that should help with the noise Sylvain commented on CASSANDRA-10848 yesterday concerning some potential problems with paging tests and whether or not we're setting the protocol version for those tests. Should be interesting to see how things look after the run with 12236 in. ~Josh
Re: when are we moving from SEDA to TPC?
On 08/03/2016 03:31 PM, Kant Kodali wrote: > when are we moving from SEDA to TPC? any timeline or something that I can > look out for? > You could follow the JIRA ticket parent and children, review patches, etc. :) https://issues.apache.org/jira/browse/CASSANDRA-10989 -- Kind regards, Michael
Re: when are we moving from SEDA to TPC?
Reference: https://issues.apache.org/jira/browse/CASSANDRA-10993 On Wed, Aug 3, 2016 at 4:31 PM, Kant Kodali wrote: > when are we moving from SEDA to TPC? any timeline or something that I can > look out for? >
when are we moving from SEDA to TPC?
when are we moving from SEDA to TPC? any timeline or something that I can look out for?
Re: Massive churn in new SSTables getting generated.
Hello Cassandra-users / Cassandra-dev, (Resending with the correct user mailing list) We have a C* 2.1.12 cluster. We have a total size of ~ 100 GB, with 2-3 GB of data being pumped in per day. We are encountering an unique situation where the SSTables are getting compacted (or it seems so) multiple times within a span of 6 hours time interval. We can conclude this by seeing different set of generation numbers on the SSTables each time, but with the same amount of data. Is this a result of compaction or repair ? Or is there any other operation that can lead to such a situation. The tables are using STCS. Thanks in advance for your help. - Rajath
Re: C* data validation in new DC
Hi, Only a repair between each DC (i.e. on the whole cluster) can guarantee that your DCs are synced. You can make some checks like data size, estimation of number of keys, etc. but it's not accurate at all. Note: your question is intended to u...@cassandra.apache.org Best, Romain Le Mercredi 3 août 2016 6h50, Ashish Pandey a écrit : 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