RE: problem with write_survey

Do you see this log message? logger.info("Startup complete, but write survey mode is active, not becoming an active ring member. Use JMX (StorageService->joinRing()) to finalize ring joining."); ð Yes ! Log : INFO [main] 2015-07-29 15:29:35,697 StorageService.java (line

Re: Reduced write performance when reading

Found the problem, it turns out that what Bharatendra suggested was correct. I had set the memtable_flush_writers to equal the number of cores but hadn't restarted the Cassandra process, so they didn't take the configuration. On Wed, Jul 29, 2015 at 12:59 PM, Robert Coli wrote: > On Tue, Jul 28,

Re: Reduced write performance when reading

On Tue, Jul 28, 2015 at 4:49 PM, Soerian Lieve wrote: > I did already set that to the number of cores of the machines (24), but it > made no difference. > I continue to suggest that you file a JIRA ticket... I feel you have done sufficient community based due dilligence to question whether this

Re: problem with write_survey

On Wed, Jul 29, 2015 at 8:04 AM, wrote: > but the node allows read: > > > > cqlsh> select * from myTable where id = 1745; > > > > id | fname | lname > > --+---+--- > > 1745 | john | smith > > This is unexpected. Does the node show up in eg nodetool ring? If so, you are probably f

Re: Leak detected during repair (v2.1.8)

https://issues.apache.org/jira/browse/CASSANDRA-9382 From: "Frisch, Michael" Reply-To: "user@cassandra.apache.org" Date: Wednesday, July 29, 2015 at 6:56 AM To: Cassandra List Subject: Leak detected during repair (v2.1.8) ERROR [Reference-Reaper:1] 2015-07-29 12:34:45,941 Ref.java:179 - LEA

problem with write_survey

Hello, I start a node with the write survey = true -Dcassandra.write_survey=true Log: INFO [main] 2015-07-29 15:29:35,697 StorageService.java (line 853) Startup complete, but write survey mode is active, not becoming an active ring member. Use JMX (StorageService->joinRing()) to finalize ring

Leak detected during repair (v2.1.8)

ERROR [Reference-Reaper:1] 2015-07-29 12:34:45,941 Ref.java:179 - LEAK DETECTED: a reference (org.apache.cassandra.utils.concurrent.Ref$State@52628658) to class org.apache.cassandra.io.sstable.SSTableReader$InstanceTidier@1113728425:/data/cassandra/data/KSName/CFName/snapshots/8179b820-35ec-11e5