Re: Phantom growth resulting automatically node shutdown

Did you check the number of files in your data folder before & after the restart? I have seen cases where cassandra would keep creating sstables, which disappeared on restart. regards, Christian On Thu, Apr 19, 2018 at 12:18 PM, Fernando Neves wrote: > I am facing one issue with our Cassandra

Re: Repair of 5GB data vs. disk throughput does not make sense

Hi Thomas, I don't think I have seen compaction ever being faster. For me, tables with small values usually are around 5 MB/s with a single compaction. With larger blobs (few KB per blob) I have seen 16MB/s. Both with "nodetool setcompactionthroughput 0". I don't think its disk related either. I

CAS operation does not return value on failure

Hi, I am doing some testing on CAS operations and I am frequently having the issue that my resultset says wasApplied()==false, but it does not contain any value. This behaviour of course leads to the following Exception when I try to read it: Caused by: java.lang.IllegalArgumentException: value

Re: CAS operation does not return value on failure

y 4, 2016 at 11:46 AM, horschi wrote: > >> Hi, >> >> I am doing some testing on CAS operations and I am frequently having the >> issue that my resultset says wasApplied()==false, but it does not contain >> any value. >> >> >> This behaviou

Re: CAS operation does not return value on failure

uot;value" column, or are you > supplying that name when executing the prepared statement? > > The "datastax.driver.core" in the exception trace class names indicates > that the error is detected in the Java driver, not Cassandra. > > > > -- Jack Krupansky > > On Thu, May 5,

Re: CAS operation does not return value on failure

I just retried with Cassandra 3.0.5 and it performs much better. Not a single of these illegal results. I guess my recommendation for anyone using CAS is: Upgrade to >= 3.x :-) On Wed, May 4, 2016 at 5:46 PM, horschi wrote: > Hi, > > I am doing some testing on CAS operati

Re: CAS operation does not return value on failure

Update: It was actually the driver update (from 2.1.9 to 3.0.1) that solved the issue. I reverted by C* Server back to 2.2 and my test is still ok. On Mon, May 9, 2016 at 1:28 PM, horschi wrote: > I just retried with Cassandra 3.0.5 and it performs much better. Not a > single of these i

C* 2.2.7 ?

Hi, are there any plans to release 2.2.7 any time soon? kind regards, Christian

Re: C* 2.2.7 ?

t; +1 >> >> there's some bugs fixed we might be or sure are affected by and the >> change log has become quite large already mind voting von 2.2.7 soon? >> >> >> Am 21.06.2016 um 15:31 schrieb horschi: >> >> Hi, >> >

Re: [RELEASE] Apache Cassandra 3.0.8 released

Same for 2.2.7. On Thu, Jul 7, 2016 at 10:49 AM, Julien Anguenot wrote: > Hey, > > The Debian packages do not seem to have been published. Normal? > > Thank you. > >J. > > On Jul 6, 2016, at 4:20 PM, Jake Luciani wrote: > > The Cassandra team is pleased to announce the release of Apache Cas

Re: [RELEASE] Apache Cassandra 3.0.8 released

> On Thu, Jul 7, 2016 at 4:51 AM, horschi wrote: > >> Same for 2.2.7. >> >> On Thu, Jul 7, 2016 at 10:49 AM, Julien Anguenot >> wrote: >> >>> Hey, >>> >>> The Debian packages do not seem to have been published. Normal? >>> >>

Re: Stale value appears after consecutive TRUNCATE

Hi Yuji, can you reproduce the behaviour with a single node? The reason I ask is because I probably have the same issue with my automated tests (which run truncate between every test), which run on my local laptop. Maybe around 5 tests randomly fail out of my 1800. I can see that the failed test

Re: Stale value appears after consecutive TRUNCATE

dscardSSTables() at truncating a table when there is no SSTable. > I guess that ReplayPosition.segment shouldn't be -1 at truncating a table > in this case. > replayMutation() can request unexpected replay mutations because of this > segment's value. > > Is there anyone fam

Re: Stale value appears after consecutive TRUNCATE

1000 > 10 | 1000 >1 | 1000 >8 | 1000 > 2 | 1000 >4 | 1000 >7 | 1000 >6 | 1000 >9 | 1000 >3 | 1000 > > (10 rows) > > > > > Thanks Christian, > > I tried with durable_writes=False. > It failed. I guess

Re: Stale value appears after consecutive TRUNCATE

(running C* 2.2.7) On Thu, Aug 25, 2016 at 11:10 AM, horschi wrote: > Hi Yuji, > > I tried your script a couple of times. I did not experience any stale > values. (On my Linux laptop) > > regards, > Ch > > On Mon, Aug 15, 2016 at 7:29 AM, Yuji Ito wrote: > &g

Re: Stale value appears after consecutive TRUNCATE

; commitlog_sync: batch > commitlog_sync_batch_window_in_ms: 2 > > The problem didn't occur by setting commitlog_sync periodic(default). > > regards, > yuji > > > On Thu, Aug 25, 2016 at 6:11 PM, horschi wrote: > >> (running C* 2.2.7) >> >> On Thu, Au

Re: Java Driver - Specifying parameters for an IN() query?

Hi Ali, do you perhaps want "'Select * from my_table WHERE pk = ? And ck IN ?'" ? (Without the brackets around the question mark) regards, Ch On Tue, Oct 11, 2016 at 3:14 PM, Ali Akhtar wrote: > If I wanted to create an accessor, and have a method which does a query > like this: > > 'Select *

Re: Speeding up schema generation during tests

Have you tried starting Cassandra with -Dcassandra.unsafesystem=true ? On Wed, Oct 19, 2016 at 9:31 AM, DuyHai Doan wrote: > As I said, when I bootstrap the server and create some keyspace, sometimes > the schema is not fully initialized and when the test code tried to insert > data, it fails.

Re: Speeding up schema generation during tests

ALL.forEach(table -> FBUtilities.waitOnFuture(getSc >> hemaCFS(table).forceFlush())); >> } >> >> I don't know how it worked out for you but it didn't for me... >> >> On Wed, Oct 19, 2016 at 9:45 AM, DuyHai Doan >> wrote:

Re: All subsequent CAS requests time out after heavy use of new CAS feature

re competing for locks and hit a > deadlock issue. > > Regards, > Denise > Cell - (860)989-3431 <(860)%20989-3431> > > Sent from mi iPhone > > On Apr 15, 2016, at 9:00 AM, horschi wrote: > > Hi Denise, > > in my case its a small blob I am writ

Re: All subsequent CAS requests time out after heavy use of new CAS feature

/CASSANDRA-8672 On Thu, Dec 15, 2016 at 3:14 PM, horschi wrote: > Hi, > > I would like to warm up this old thread. I did some debugging and found > out that the timeouts are coming from StorageProxy.proposePaxos() > - callback.isFullyRefused() returns false and therefore triggers a

Re: All subsequent CAS requests time out after heavy use of new CAS feature

workload you see things timing > out and before you hit 100% CPU. It is a strange beast. > > On Fri, Dec 23, 2016 at 7:28 AM, horschi wrote: > >> Update: I replace all quorum reads on that table with serial reads, and >> now these errors got less. Somehow quorum reads on

Re: Truncate really slow

Hi, you have to enable -Dcassandra.unsafesystem=true in cassandra-env.sh. Also disable durables writes for your CFs. This should speed things up and should reduce IOWait dramatically. kind regards, Christian On Wed, Jul 1, 2015 at 11:52 PM, Robert Wille wrote: > I have two test clusters, both

auto_bootstrap=false broken?

Hi everyone, I'll just ask my question as provocative as possible ;-) Isnt't auto_bootstrap=false broken the way it is currently implemented? What currently happens: New node starts with auto_bootstrap=false and it starts serving reads immediately without having any data. Would the following be

Re: auto_bootstrap=false broken?

ew datacenters or > clusters, or nodes with data already on it before starting the process. > > Cheers, > > Paulo > > 2015-08-04 8:50 GMT-03:00 horschi : > >> Hi everyone, >> >> I'll just ask my question as provocative as possible ;-) >> >> Isnt&#

Re: auto_bootstrap=false broken?

: > I had problems with write_survey. > > I opened a bug : https://issues.apache.org/jira/browse/CASSANDRA-9934 > > > > *De :* horschi [mailto:hors...@gmail.com] > *Envoyé :* mardi 4 août 2015 15:20 > *À :* user@cassandra.apache.org > *Objet :* Re: auto_bootstrap=false brok

Re: auto_bootstrap=false broken?

behaviour (or at least I don't know how). kind regards, Christian On Tue, Aug 4, 2015 at 7:12 PM, Robert Coli wrote: > On Tue, Aug 4, 2015 at 6:19 AM, horschi wrote: > >> I would like to separate these steps: >> 1. assign tokens >> 2. have the node in a joinin

Re: auto_bootstrap=false broken?

Hi Jonathan, unless you specify auto_bootstrap=false :) kind regards, Christian On Tue, Aug 4, 2015 at 7:54 PM, Jonathan Haddad wrote: > You're trying to solve a problem that doesn't exist. Cassandra only > starts serving reads when it's ready. > > On Tue, Aug

Re: auto_bootstrap=false broken?

override it with nodetool. Disclaimer: I am using C* 2.0. kind regards, Christian On Tue, Aug 4, 2015 at 10:02 PM, Robert Coli wrote: > On Tue, Aug 4, 2015 at 11:40 AM, horschi wrote: > >> unless you specify auto_bootstrap=false :) >> > > ... so why are you doing t

Re: auto_bootstrap=false broken?

Hi Rob, > Your asking the wrong nodes for data in the rebuild-a-new-DC case does not > indicate a problem with the auto_bootstrap false + rebuild paradigm. > The node is "wrong" only because its currently bootstrapping. So imho Cassandra should not serve any reads in such a case. > > What ma

Re: auto_bootstrap=false broken?

Hi Jeff, You’re trying to force your view onto an established ecosystem. > It is not my intent to force anyone to do anything. I apologize if my title was too provocative. I just wanted to clickbait ;-) It’s not “wrong only because its currently bootstrapping”, it’s not > bootstrapping at all,

Re: auto_bootstrap=false broken?

Hi Cyril, thanks for backing me up. I'm under siege from all sides here ;-) That something we're trying to do too. However disabling clients > connections (closing thrift and native ports) does not prevent other nodes > (acting as a coordinators) to request it ... Honestly we'd like to restart >

Re: Is it possible to bootstrap the 1st node of a new DC?

Hi Tom, this sounds very much like my thread: "auto_bootstrap=false broken?" Did you try booting the new node with survey-mode? I wanted to try this, but I am waiting for 2.0.17 to come out (survey mode is broken in earlier versions). Imho survey mode is what you (and me too) want: start a node,

Re: Is it possible to bootstrap the 1st node of a new DC?

e > mysteriously routed to the new DC every now and then. > > Currently I'm trying to auto_bootstrap my new DC. The good thing is that > it doesn't accept reads from other DCs. The bad thing is that a) I can't > choose where it streams its data from, and b) the two nod

Re: Is it possible to bootstrap the 1st node of a new DC?

the bootstrapping begins. >>> >>> It turns out that join_ring=false in this scenario does not solve this >>> problem, since nodetool rebuild does not do anything if C* is started with >>> this option. >>> >>> A workaround could be to ensure that on

Re: Is it possible to bootstrap the 1st node of a new DC?

at 9:05 PM, Robert Coli wrote: > > > On Tue, Sep 8, 2015 at 1:39 AM, horschi wrote: > >> "The idea of join_ring=false is that other nodes are not aware of the >> new node, and therefore never send requests to it. The new node can then be >> repaired" >&g

Re: Is it possible to bootstrap the 1st node of a new DC?

ensure consistency. - Finish bootstrap. Now node1 should not be responsible for the range and node4 should become eligible for reads. regards, Christian On Tue, Sep 8, 2015 at 11:51 PM, Robert Coli wrote: > On Tue, Sep 8, 2015 at 2:39 PM, horschi wrote: > >> I tried to set up

Re: Is it possible to bootstrap the 1st node of a new DC?

solved in cassandra 2.1 (see CASSANDRA-2434). > Regards, > Samuel > > > horschi a écrit sur 10/09/2015 12:41:41 : > > > De : horschi > > A : user@cassandra.apache.org, > > Date : 10/09/2015 12:42 > > Objet : Re: Is it possible to bootstrap the 1st node

Re: memory usage problem of Metadata.tokenMap.tokenToHost

Hi Joseph, I think 2000 keyspaces might be just too much. Fewer keyspaces (and CFs) will probably work much better. kind regards, Christian On Tue, Sep 22, 2015 at 9:29 AM, joseph gao wrote: > Hi, anybody could help me? > > 2015-09-21 0:47 GMT+08:00 joseph gao : > >> ps : that's the code in j

Re: 3k sstables during a repair incremental !!

Hi Jean, which Cassandra version do you use? Incremental repair got much better in 2.2 (for us at least). kind regards, Christian On Wed, Feb 10, 2016 at 2:33 PM, Jean Carlo wrote: > Hello guys! > > I am testing the repair inc in my custer cassandra. I am doing my test over > these tables > >

Re: 3k sstables during a repair incremental !!

10, 2016 at 2:46 PM, Jean Carlo wrote: > Hi Horschi !!! > > I have the 2.1.12. But I think it is something related to Level compaction > strategy. It is impressive that we passed from 6 sstables to 3k sstable. > I think this will affect the latency on production because the number o

Re: 3k sstables during a repair incremental !!

btw: I am not saying incremental Repair in 2.1 is broken, but ... ;-) On Wed, Feb 10, 2016 at 2:59 PM, horschi wrote: > Hi Jean, > > we had the same issue, but on SizeTieredCompaction. During repair the > number of SSTables and pending compactions were exploding. > > It

Low compactionthroughput blocks reads?

Hi, I just had a weird behaviour on one of our Cassandra nodes, which I would like to share: Short version: My pending reads went up from ~0 to the hundreds when I reduced the compactionthroughput from 16 to 2. Long version: One of our more powerful nodes had a few pending reads, while the oth

Dynamic TTLs / limits still not working in 2.2 ?

Hi, according to CASSANDRA-4450 it should be fixed, but I still can't use dynamic TTLs or limits in my CQL queries. Query: update mytable set data=:data where ts=:ts and randkey=:randkey using ttl :timetolive Exception: Caused by: com.datast

Re: Dynamic TTLs / limits still not working in 2.2 ?

k is to use an unnamed bind marker for the > TTL ('?') and then set it using the "[ttl]" reserved name as the bind > marker name ('setLong("[ttl]", myTtl)'), which will set the correct field > in the bound statement. > > > Best, > >

Re: Dynamic TTLs / limits still not working in 2.2 ?

is is the issue with my "select ... limit" querys. But I will verify this and also try the workaround. On Tue, Mar 8, 2016 at 3:08 PM, horschi wrote: > Hi Nick, > > I will try your workaround. Thanks a lot. > > I was not expecting the Java-Driver to have a bug, because in

Re: Dynamic TTLs / limits still not working in 2.2 ?

Ok, I just realized the parameter should not be called ":limit" :-) Also I upgraded my Java Driver from 2.1.6 to 2.1.9. Both, TTL and limit, work fine now. Sorry again for the confusion. cheers, Christian On Tue, Mar 8, 2016 at 3:19 PM, horschi wrote: > Oh, I just realized I m

Re: All subsequent CAS requests time out after heavy use of new CAS feature

Hi Jan, were you able to resolve your Problem? We are trying the same and also see a lot of WriteTimeouts: WriteTimeoutException: Cassandra timeout during write query at consistency SERIAL (2 replica were required but only 1 acknowledged the write) How many clients were competing for a lock in y

Re: All subsequent CAS requests time out after heavy use of new CAS feature

data were you reading/writing? > > Regards, > Denise > > Sent from mi iPad > > On Apr 15, 2016, at 8:29 AM, horschi wrote: > > Hi Jan, > > were you able to resolve your Problem? > > We are trying the same and also see a lot of WriteTimeouts: > WriteTimeoutE

Re: Cassandra Evaluation/ Benchmarking: Throughput not scaling as expected neither latency showing good numbers

When they say "linear scalibility" they mean "throughput scales with the amount of machines in your cluster". Try adding more machines to your cluster and measure the thoughput. I'm pretty sure you'll see linear scalibility. regards, Christian On Tue, Jul 17, 2012 at 6:13 AM, Code Box wrote:

Re: are counters stable enough for production?

"The repair of taking the highest value of two inconsistent might cause getting higher values?" If a counter counts backwards (therefore has negative values), then repair would still choose the larger value? Or does cassandra take the highter absolute value? This would result to an undercounting

Re: Cassandra vs Couchbase benchmarks

Hi Andy, things I find odd: - Replicacount=1 for mongo and couchdb. How is that a realistic benchmark? I always want at least 2 replicas for my data. Maybe thats just me. - On the Mongo Config slide they said they disabled journaling. Why do you disable all safety mechanisms that you would want i

Re: repair, compaction, and tombstone rows

Hi Sylvain, might I ask why repair cannot simply ignore anything that is older than gc-grace? (like Aaron proposed) I agree that repair should not process any tombstones or anything. But in my mind it sounds reasonable to make repair ignore timed-out data. Because the timestamp is created on the

Re: repair, compaction, and tombstone rows

> IIRC, tombstone timestamps are written by the server, at compaction > time. Therefore if you have RF=X, you have X different timestamps > relative to GCGraceSeconds. I believe there was another thread about > two weeks ago in which Sylvain detailed the problems with what you are > proposing, when

Re: repair, compaction, and tombstone rows

is ensured that repair ran and any previous un-TTLed columns were overwritten. - ... ExpiringColumn not add local timestamp to digest? Cheers, Christian On Sat, Nov 3, 2012 at 8:37 PM, Sylvain Lebresne wrote: > On Fri, Nov 2, 2012 at 10:46 AM, horschi wrote: > > might I ask why repair c

Re: repair, compaction, and tombstone rows

> - ... ExpiringColumn not create any tombstones? Imo this could be safely > > done if the columns TTL is >= gcgrace. > > Yes, if the TTL >= gcgrace this would be safe and I'm pretty sure we > use to have a ticket for that (can't find it back with a quick search > but JIRA search suck and I didn't

Re: repair, compaction, and tombstone rows

That's true, we could just create an already gcable tombstone. It's a bit > of an abuse of the localDeletionTime but why not. Honestly a good part of > the reason we haven't done anything yet is because we never really had > anything for which tombstones of expired columns where a big pain point. >

Re: repair, compaction, and tombstone rows

use TTLs or do you think its due to DeletedColumns? Was your intension to push the idea of removing localDeletionTime from DeletedColumn.updateDigest ? cheers, Christian > > On Mon, Nov 5, 2012 at 5:12 PM, horschi wrote: > >> >> >> That's true, we could just create

Re: repair, compaction, and tombstone rows

I don't know enough about the code level implementation to comment on the > validity of the fix. My main issue is that we use a lot of TTL columns and > in many cases all columns have a TTL that is less than gc_grace. The > problem arises when the columns are gc-able and are compacted away on one

Re: Driver consistency issue

Hi Abhishek & everyone else, might it be related to https://issues.apache.org/jira/browse/CASSANDRA-7868 ? regards, Christian On Tue, Feb 27, 2018 at 12:46 PM, Abhishek Kumar Maheshwari < abhishek.maheshw...@timesinternet.in> wrote: > Hi, > > Not always. Randomly i am getting this exception.

Re: How do you run integration tests for your cassandra code?

Hi Kevin, I run my tests against my locally running Cassandra instance. I am not using any framework, but simply truncate all my tables after/before each test. With which I am quite happy. You have to enable the unsafeSystem property, disable durable writes on the CFs and disable auto-snapshot in

Query returning tombstones

Hi, did anybody ever raise a feature request for selecting tombstones in CQL/thrift? It would be nice if I could use CQLSH to see where my tombstones are coming from. This would much more convenient than using sstable2json. Maybe someone can point me to an existing jira-ticket, but I also apprec

Re: Query returning tombstones

://issues.apache.org/jira/browse/CASSANDRA-8574?focusedCommentId=14292063&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-14292063 > > Cheers, > Jens > > On Wed, Apr 29, 2015 at 12:43 PM, horschi wrote: > >> Hi, >> >> did anyb

Re: How to minimize Cassandra memory usage for test environment?

Hi Eax, are you truncating/dropping tables between tests? Are your issues perhaps related to that? If you are, you should disable autoSnapshots and enable -DunsafeSystem=true to make it run smoother. kind regards, Christian On Tue, Jun 9, 2015 at 11:25 AM, Jason Wee wrote: > for a start, mayb

Murmur Long.MIN_VALUE token allowed?

Hi, I just realized that I can move a node to Long.MIN_VALUE: 127.0.0.1 rack1 Up Normal 1011.58 KB 100.00% -9223372036854775808 Is that really a valid token for Murmur3Partitioner ? I thought that Long.MIN_VALUE (like -1 for Random) is not a regular token. Shouldn't be only use

Re: Murmur Long.MIN_VALUE token allowed?

onsulting > http://www.thelastpickle.com > > On 5/12/2013, at 12:38 am, horschi wrote: > > Hi, > > I just realized that I can move a node to Long.MIN_VALUE: > > 127.0.0.1 rack1 Up Normal 1011.58 KB 100.00% > -9223372036854775808 > > Is that really

Offline migration: Random->Murmur

Hi list, has anyone ever tried to migrate a cluster from Random to Murmur? We would like to do so, to have a more standardized setup. I wrote a small (yet untested) utility, which should be able to read SSTable files from disk and write them into a cassandra cluster using Hector. This migration w

Re: Offline migration: Random->Murmur

; the production traffic. I was able to do this on a non prod cluster, but > production is a different game. > > I would also like to hear more about this, especially if someone was able > to successfully do this. > > Thanks > Rahul > > > On Mon, Dec 23, 2013 at 6:45 PM,

Re: Cassandra unit testing becoming nearly impossible: suggesting alternative.

Hi Ed, my opinion on unit testing with C* is: Use the real database, not any embedded crap :-) All you need are fast truncates, by which I mean: JVM_OPTS="$JVM_OPTS -Dcassandra.unsafesystem=true" and auto_snapshot: false This setup works really nice for me (C* 1.1 and 1.2, have not tested 2.0 ye

Re: Possible optimization: avoid creating tombstones for TTLed columns if updates to TTLs are disallowed

Hi Donald, I was reporting the ticket you mentioned, so I kinds feel like I should answer this :-) I presume the point is that GCable tombstones can still do work > (preventing spurious writing from nodes that were down) but only until the > data is flushed to disk. > I am not sure I understand

Re: Expired column showing up

Hi Mahesh, is it possible you are creating columns with a long TTL, then update these columns with a smaller TTL? kind regards, Christian On Fri, Feb 14, 2014 at 3:45 PM, mahesh rajamani wrote: > Hi, > > I am using Cassandra 2.0.2 version. On a wide row (approx. 1 columns), > I expire few

Re: Expired column showing up

you can explain why you are doing this? kind regards, Christian On Mon, Feb 17, 2014 at 6:18 PM, mahesh rajamani wrote: > Christain, > > Yes. Is it a problem? Can you explain what happens in this scenario? > > Thanks > Mahesh > > > On Fri, Feb 14, 2014 at 3:07

Does NetworkTopologyStrategy in Cassandra 2.0 work?

Hi, is it possible that NetworkTopologyStrategy does not work with Cassandra 2.0 any more? I just updated my Dev Cluster to 2.0.7 and got UnavailableExceptions for CQL&Thrift queries on my already existing column families, even though all (two) nodes were up. Changing to SimpleStrategy fixed the

Re: Does NetworkTopologyStrategy in Cassandra 2.0 work?

s wrong, but 1.2 did not care about it. cheers, Christian On Tue, Apr 22, 2014 at 1:51 PM, horschi wrote: > Hi, > > is it possible that NetworkTopologyStrategy does not work with Cassandra > 2.0 any more? > > I just updated my Dev Cluster to 2.0.7 and got UnavailableExc

Cassandra 2.0.8 MemoryMeter goes crazy

Hi everyone, this week we upgraded one of our Systems from Cassandra 1.2.16 to 2.0.8. All 3 nodes were upgraded. SStables are upgraded. Unfortunetaly we are now experiencing that Cassandra starts to hang every 10 hours or so. We can see the MemoryMeter being very active, every time it is hanging

Re: Cassandra 2.0.8 MemoryMeter goes crazy

Hi again, before people start replying here: I just reported a Jira ticket: https://issues.apache.org/jira/browse/CASSANDRA-7401 I think Memtable.maybeUpdateLiveRatio() needs some love. kind regards, Christian On Sat, Jun 14, 2014 at 10:02 PM, horschi wrote: > Hi everyone, > > thi

Re: Cassandra 2.0.8 MemoryMeter goes crazy

PM, horschi wrote: > >> this week we upgraded one of our Systems from Cassandra 1.2.16 to 2.0.8. >> All 3 nodes were upgraded. SStables are upgraded. >> > > One of your *clusters* or one of your *systems*? > > Running with split major versions is not supported. > > =Rob >

Re: MemtablePostFlusher and FlushWriter

I have seen this behavour when Commitlog files got deleted (or permissions were set to read only). MemtablePostFlusher is the stage that marks the Commitlog as flushed. When they fail it usually means there is something wrong with the commitlog files. Check your logfiles for any commitlog related

Re: MemtablePostFlusher and FlushWriter

k : > > The MemtablePostFlusher is also used for flushing non-cf backed (solr) >> indexes. Are you using DSE and solr by chance? >> >> Chris >> >> On Jul 15, 2014, at 5:01 PM, horschi wrote: >> >> I have seen this behavour when Commitlog files got del

Re: MemtablePostFlusher and FlushWriter

time blocked' > > Thanks, > > > 2014-07-16 16:23 GMT+02:00 horschi : > > Hi Ahmed, >> >> this exception is caused by you creating rows with a key-length of more >> than 64kb. Your key is 394920 bytes long it seems. >> >> Keys and column-names are limit

Re: Repair does not fix inconsistency

Hi Michal, Let's say the tombstone on one of the nodes (X) is gcable and was not > compacted (purged) so far. After it was created we re-created this row, but > due some problems it was written only to the second node (Y), so we have > "live" data on node Y which is newer than the gcable tombstone

Re: Repair does not fix inconsistency

Hi, This was my first thought too, but if you take a look at the logs I > attached to previous e-mail, you'll notice that query "by key" > (no-index.log) retrieves data from BOTH replicas, while the "by indexed > column" one (index.log) talks only to one of them (too bad it's the one > that contai

Re: Repair does not fix inconsistency

> Well... Strange. We have such problem with 6 users, but there's only ONE > tombstone (created 8 days ago, so it's not gcable yet) in all the SSTables > on 2:1 node - checked using sstable2json. > Moreover, this tombstone DOES NOT belong to the row key I'm using for > tests, because this user was

Re: Repair does not fix inconsistency

Repair is fine - all the data seem to be in SSTables. I've checked it and > while index tells me that I have 1 tombstone and 0 live cells for a key, I > can _see_, thanks to sstable2json, that I have 3 "live cells" (assuming a > cell is an entry in SSTable) and 0 tombstones. After being confused fo

Re: MySQL Cluster performing faster than Cassandra cluster on single table

Hi Hannah, mysql-cluster is a in-memory database. In-memory is fast. But I dont think you ever be able to store hundreds of Gigabytes of data on a node, which is something you can do with Cassandra. If your dataset is small, then maybe NDB is the better choice for you. I myself will not even tou

Re: MySQL Cluster performing faster than Cassandra cluster on single table

Ah, I see, that makes sense. Have you got a source for the storing of > hundreds of gigabytes? And does Cassandra not store anything in memory? > It stores bloom filters and index-samples in memory. But they are much smaller than the actual data and they can be configured. > > Yeah, my dataset is

Re: (unofficial) Community Poll for Production Operators : Repair

Hi Alain, have you had a look at the following tickets? CASSANDRA-4905 - Repair should exclude gcable tombstones from merkle-tree computation CASSANDRA-4932 - Agree on a gcbefore/expirebefore value for all replica during validation compaction CASSANDRA-4917 - Optimize tombstone creation for Expir

Cassandra 1.1.11 does not always show filename of corrupted files

Hi, we had some hard-disk issues this week, which caused some datafiles to get corrupt, which was reported by the compaction. My approach to fix this was to delete the corrupted files and run repair. That sounded easy at first, but unfortunetaly C* 1.1.11 sometimes does not show which datafile is

Re: Cassandra 1.1.11 does not always show filename of corrupted files

(), chunk); } So thats nice :-) But does nobody else find the old behaviour annoying? Nobody ever wanted to identfy the broken files? cheers, Christian On Thu, May 30, 2013 at 7:11 PM, horschi wrote: > Hi, > > we had some hard-disk issues this week, which caused some datafil

Re: Compacted data returns with repair?

Hi, this sounds like the following issue: https://issues.apache.org/jira/browse/CASSANDRA-4905 cheers, Ch On Tue, Jun 4, 2013 at 5:50 PM, André Cruz wrote: > Hello. > > I deleted a lot of data from one of my CFs, waited the gc_grace_period, > and as the compactions were deleting the data slow

Re: Cassandra optimizations for multi-core machines

Hi, Cassandra is heavily multithreaded. If the load demands it will make use of your 8 cores. I dont know the startup code, but I would assume it would be parallelized if neccessary/possible. Afaik there were optimizations already made to reduce the startup time. Therefore I would assume any opti

C* 1.2.5 AssertionError in ColumnSerializer:40

Hi, using C* 1.2.5 I just found a weird AssertionError in our logfiles: ... INFO [OptionalTasks:1] 2013-07-01 09:15:43,608 MeteredFlusher.java (line 58) flushing high-traffic column family CFS(Keyspace='Monitoring', ColumnFamily='cfDateOrderedMessages') (estimated 5242880 bytes) INFO [OptionalT

Re: TTL, Tombstones, and gc_grace

Hi Michael, yes, you should never loose a delete, because there are no real deletes. No matter what version you are using. btw: There is actually a ticket that builds an optimization on top of that assumption: CASSANDRA-4917. Basically, if TTL>gc_grace then do not create tombstones for expiring-c

Re: About column family

With 1.2.7 you can use -Dcassandra.unsafesystem. That will speed up cf creation. So you will get in even more trouble even faster! On Tue, Jul 23, 2013 at 12:23 PM, bjbylh wrote: > Hi all: > i have two questions to ask: > 1,how many column families can be created in a cluster?is there a limit

Re: How often to run `nodetool repair`

> TTL is effectively DELETE; you need to run a repair once every > gc_grace_seconds. If you don't, data might un-delete itself. > The undelete part is not true. btw: With CASSANDRA-4917 TTLed columns will not even create a tombstone (assuming ttl > gc_grace). The rest of your mail I agree with :-

Re: TTL and gc_grace_Seconds

Hi Christopher, in 2.0 gc_grace should be capped by TTL anyway: see CASSANDRA-4917 cheers, Christian On Wed, Sep 18, 2013 at 4:29 PM, Christopher Wirt wrote: > I have a column family contains time series events, all columns have a 24 > hour TTL and gc_grace_seconds is currently 20 days. There