Re: node decommission throttled

Maybe your System cannot Stream faster. Is your cpu or hd/ssd fully utilized? Am 07.12.2016 16:07 schrieb "Eric Evans" : > On Tue, Dec 6, 2016 at 9:54 AM, Aleksandr Ivanov wrote: > > I'm trying to decommission one C* node from 6 nodes cluster and see

Re: Cassandra MV insert Warning

tors.java:511) ~[na:1.8.0_65] at > org.apache.cassandra.concurrent.AbstractLocalAwareExecutorServ > ice$FutureTask.run(AbstractLocalAwareExecutorService.java:164) > ~[apache-cassandra-3.7.0.jar:3.7.0] at org.apache.cassandra. > concurrent.SEPWorker.run(SEPWorker.java:105) > [apache-

Re: Strange issue wherein cassandra not being started from cron

s gets killed (reason unknown as of now). > > That's why you have a cluster of them. > > Best >Martin > -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880-6 · Fax +49 7161 304880-1 AG Ulm · HRB 731058 · Managing Director: Jens Kammerer

Re: Strange issue wherein cassandra not being started from cron

I think you should take a look at supervisord or sth similar. This is a much more reliable solution than using crons. Am 12.01.2017 06:12 schrieb "Ajay Garg" : On Wed, Jan 11, 2017 at 8:29 PM, Martin Schröder wrote: > 2017-01-11 15:42 GMT+01:00 Ajay

Re: implementing a 'sorted set' on top of cassandra

~every five minutes or so) >3. Write back to a different CF with the ordered keys I care about > > Does this seem crazy? Is there a simpler way to do this in cassandra? > -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880

Re: implementing a 'sorted set' on top of cassandra

Not if you want to sort by score (a counter) Am 14.01.2017 08:33 schrieb "DuyHai Doan" : > Clustering column can be seen as sorted set > > Table abstraction == Map> > > > On Sat, Jan 14, 2017 at 2:28 AM, Edward Capriolo > wrote: > >> >> >> On Fri,

Re: Trying to identify the cause of these errors.

AbstractLocalAwareExecutorService.java:136) > [apache-cassandra-3.3.0.jar:3.3.0] > at org.apache.cassandra.concurrent.SEPWorker.run(SEPWorker.java:105) > [apache-cassandra-3.3.0.jar:3.3.0] > at java.lang.Thread.run(Thread.java:745) [na:1.8.0_111] > Caused by: java.lang.NullPointerExcep

Re: implementing a 'sorted set' on top of cassandra

ter type but then no sorting is possible since counter >> cannot be used as type for clustering column (which allows sort) >> >> Or use simple numeric type on clustering column but then to increment the >> value *concurrently* and *safely* it's prohibitive (SELECT to fetch cu

Re: Change primary key from int to bigint

gt; > bigint and int have incompatible serialization types, so that won't work. > However, changing to 'varint' will work fine. > > Hope that helps. > > Tom > > > > On Wed, Jan 11, 2017 at 9:21 AM, Benjamin Roth <benjamin.r...@jaumo.com> > wrote: > >> H

Change primary key from int to bigint

or does the SSTable serialization and maybe the token generation require the tables to be completely reread+rewritten? -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880-6 · Fax +49 7161 304880-1 AG Ulm · HRB 731058 · Managing Director: Jens Kammerer

Re: Change primary key from int to bigint

--+--- >16777215 | test >16777216 | test > 2147483647 | test > > (3 rows) > cqlsh> select * from foo; > > id | value > +--- > 128 | test >16777216 | test > 1 | test > 2147483647 | test >16777215 | test >

Re: Change primary key from int to bigint

16777216 | test > 1 | test > 2147483647 | test >16777215 | test > 256 | test > 65535 | test > 65536 | test > > > > > On Wed, Jan 11, 2017 at 9:54 AM, Benjamin Roth <benjamin.r...@jaumo.com> > wrote: > >>

Re: Queries execution time

vat...@gmail.com>: > Hi, > Does anyone know if there is a way to record in a log file the queries > total or partial execution time? I am interested in something similar to > the tracing option but on file. > > Thanks > Best Regards > Salvatore > -- Benjamin Roth Prok

Re: Cassandra 2.x Stability

disclose or take action based on this >> message or any information herein. >> If you have received this message in error, please advise the sender >> immediately by reply email and delete this message. Thank you. >> >> >> >> This message may contain confi

Re: Cassandra: maximum size of collection list type

You can read it in the docs but i think it was 2^16 aka 64k Am 01.12.2016 18:00 schrieb "Selvam Raman" : > Hi, > > What is the maximum size which can be stored into collection list(in a row > ) in cassandra. > > -- > Selvam Raman > "லஞ்சம் தவிர்த்து நெஞ்சம் நிமிர்த்து" >

Re: Which version is stable enough for production environment?

se/CASSANDRA-12844 > > > Also when i testes some of our write heavy workload Leveled Compaction was > not keeping up.With same system settings 2.1.16 performs better and all > levels was properly aligned. > -- > *From:* Benjamin Roth <benjamin.r...

Re: Cassandra 2.x Stability

-12-01 19:14 GMT+01:00 Kai Wang <dep...@gmail.com>: > Ben, I just read through those two tickets. It's scarier than I thought. > Thank you for all the investigations and comments. > > On Thu, Dec 1, 2016 at 10:31 AM, Benjamin Roth <benjamin.r...@jaumo.com> > wrote: >

Re: Which version is stable enough for production environment?

loy Cassandra in production env, but we > can not confirm which version is stable and recommended, could someone in > this mail list give the suggestion? Thanks in advance! > > > Best Regards > Discovery > 11/30/2016 > -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880-6 · Fax +49 7161 304880-1 AG Ulm · HRB 731058 · Managing Director: Jens Kammerer

Re: Which version is stable enough for production environment?

ue > and let us know. We're well aware of the issues affecting MVs, but they > haven't really been solved anywhere yet. > > On 30 November 2016 at 07:54, Benjamin Roth <benjamin.r...@jaumo.com> > wrote: > >> Hi Brooke, >> >> Just had a quick look on

Re: Which version is stable enough for production environment?

nt, do not copy or disclose its content, but please reply > to this email immediately and highlight the error to the sender and then > immediately delete the message. > > On 30 November 2016 at 18:20, Benjamin Roth <benjamin.r...@jaumo.com> > wrote: > >> What are the comp

Re: Why does `now()` produce different times within the same query?

Great comment. +1 Am 01.12.2016 06:29 schrieb "Ben Bromhead" : > tl;dr +1 yup raise a jira to discuss how now() should behave in a single > statement (and possible extend to batch statements). > > The values of now should be the same if you assume that now() works like > it

Re: Sanity checks to run post restore data?

ing up sstables, and need to learn, what sanity > checks should be performed after restoring them? > > Thanks, > Varun > -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880-6 · Fax +49 7161 304880-1 AG Ulm · HRB 73

Re: Which version is stable enough for production environment?

y written hint files. Agile >>> Board; Awaiting Feedback; Export >>> https://issues.apache.org/jira/browse/CASSANDRA-12844 >>> >>> >>> Also when i testes some of our write heavy workload Leveled Compaction >>> was not keeping up.With same system

Re: Why does Cassandra recommends Oracle JVM instead of OpenJDK?

Does this discussion really make sense any more? To me it seems it turned opinionated and religious. From my point of view anything that has to be said was said. Am 02.01.2017 21:27 schrieb "Edward Capriolo" : > > > On Mon, Jan 2, 2017 at 11:56 AM, Eric Evans

Re: All nodes hosting replicas down

; >> On Sun, Dec 18, 2016 at 7:47 PM, jean paul <researche...@gmail.com> >> wrote: >> >>> Hi, >>> >>> Please, if we choose a replication factor =2 (simple strategy), so, we >>> have two replicas of data on the ring. >>> >>&g

Re: Materialised view for sets of UUID

, > because the second variant has to go through many rows to collect > all non-deleted clustering key values. Write performance is > slightly better for the first variant because one table + two > materialised views is more expensive than two tables. > > What would you prefer? > > Tschö, > Torsten. > > -- > Torsten Bronger > > -- Benjamin Roth Prokurist Jaumo GmbH · www.jaumo.com Wehrstraße 46 · 73035 Göppingen · Germany Phone +49 7161 304880-6 · Fax +49 7161 304880-1 AG Ulm · HRB 731058 · Managing Director: Jens Kammerer

Re: Batch size warnings

Could you please be more specific? Am 07.12.2016 17:10 schrieb "Voytek Jarnot" : > Should've mentioned - running 3.9. Also - please do not recommend MVs: I > tried, they're broken, we punted. > > On Wed, Dec 7, 2016 at 10:06 AM, Voytek Jarnot >

Re: Running cassandra

I once had the same problem. In my case it was the coloured output of grep that injected ansi codes into the CS startup command. Am 19.03.2017 18:07 schrieb "Long Quanzheng" : > Hi > It still doesn't work. > > The real problem is this error: > > Error: Could not find or load

Re: Running cassandra

You're welcome! 2017-03-19 18:41 GMT+01:00 Long Quanzheng <prc...@gmail.com>: > You are RIGHT! > It's working after I remove the env variable GREP_OPTIONS. > > Thanks! > > 2017-03-19 10:08 GMT-07:00 benjamin roth <brs...@gmail.com>: > >>

Re: repair performance

It depends a lot ... - Repairs can be very slow, yes! (And unreliable, due to timeouts, outages, whatever) - You can use incremental repairs to speed things up for regular repairs - You can use "reaper" to schedule repairs and run them sliced, automated, failsafe The time repairs actually may

Re: repair performance

b > threads: 1, ColumnFamilies: [], dataCenters: [ProdDC2], hosts: [], # of > ranges: 1758) > > 3.0.7 is also the reason why we are not using reaper ... as far as i could > figure out it's not compatible with 3.0+ > > > > On Fri, 2017-03-17 at 22:13 +0100, benjamin roth wrote: >

Re: spikes in blocked native transport requests

Did you check STW GCs? You can do that with 'nodetool gcstats', by looking at the gc.log or observing GC related JMX metrics. 2017-03-20 8:52 GMT+01:00 Roland Otta : > we have a datacenter which is currently used exlusively for spark batch > jobs. > > in case batch jobs

Re: Multiple nodes decommission

I did not test it but I'd bet that parallel decommision will lead to inconsistencies. Each decommission results in range movements and range reassignments which becomes effective after a successful decommission. If you start several decommissions at once, I guess the calculated reassignments are

Re: nodes are always out of sync

Btw.: I created an issue for that some months ago https://issues.apache.org/jira/browse/CASSANDRA-12991 2017-04-01 22:25 GMT+02:00 Roland Otta <roland.o...@willhaben.at>: > thank you both chris and benjamin for taking time to clarify that. > > > On Sat, 2017-04-01 at 21:17 +0

WriteTimeoutException with LWT after few milliseconds

Hi folks, Can someone explain why that occurs? Write timeout after 0.006s Query: 'INSERT INTO log_moment_import ("source", "reference", "user_id", "moment_id", "date", "finished") VALUES (3, '1305821272790495', 65675537, 0, '2017-04-12 13:00:51', NULL) IF NOT EXISTS Primary key and parition key

Re: WriteTimeoutException with LWT after few milliseconds

s not indicate that problem (as it says its > a timeout)... but in that case you would get an instant error for inserts. > wouldn't you? > > br, > roland > > > > On Wed, 2017-04-12 at 15:09 +0200, benjamin roth wrote: > > Hi folks, > > Can someone explain why that occur

Re: Node always dieing

Cassandra cannot write an SSTable to disk. Are you sure the disk/volume where SSTables reside (normally /var/lib/cassandra/data) is writeable for the CS user and has enough free space? The CDC warning also implies that. The other warnings indicate you are probably not running CS as root and you

Re: Node always dieing

> trickle_fsync_interval_in_kb=10240; truncate_request_timeout_in_ms=600; > unlogged_batch_across_partitions_warn_threshold=10; > user_defined_function_fail_timeout=1500; > user_defined_function_warn_timeout=500; > user_function_timeout_policy=die; windows_timer_interval=1; > wri

Re: Node always dieing

= 1048575 net.ipv4.tcp_keepalive_time=600 On /etc/pam.d/su ... sessionrequired pam_limits.so ... Distro is the currently Ubuntu LTS. Thanks On 04/06/2017 10:39 AM, benjamin roth wrote: Cassandra cannot write an SSTable to disk. Are you sure the disk/volume where SSTables reside (normally /var

Re: hanging validation compaction

You should connect to the node with JConsole and see where the compaction thread is stuck 2017-04-13 8:34 GMT+02:00 Roland Otta : > hi, > > we have the following issue on our 3.10 development cluster. > > we are doing regular repairs with thelastpickle's fork of

Re: Counter performance

Do you have a different compaction strategy on the counter tables? 2017-04-17 10:07 GMT+02:00 Eren Yilmaz : > We are using Cassandra (3.7) counter tables in our application, and there > are about 10 counter tables. The counter tables are in a separate keyspace > with

RE: Counter performance

e little control over Usergrid-created data. *From:* benjamin roth [mailto:brs...@gmail.com] *Sent:* Monday, April 17, 2017 4:12 PM *To:* user@cassandra.apache.org *Subject:* Re: Counter performance Do you see difference when tracing the selects? 2017-04-17 13:36 GMT+02:00 Eren

RE: Counter performance

r ways to log slow > queries in this version? Or, what do we expect with this log output? > > > > *From:* benjamin roth [mailto:brs...@gmail.com] > *Sent:* Monday, April 17, 2017 5:44 PM > *To:* user@cassandra.apache.org > *Subject:* RE: Counter performance > > > >

Re: Counter performance

changed them > to LeveledCompactionStrategy then. > > > > compaction = { 'class' : > 'org.apache.cassandra.db.compaction.LeveledCompactionStrategy', > 'sstable_size_in_mb' : 512 } > > > > *From:* benjamin roth [mailto:brs...@gmail.com] > *Sent:* Monday, April 17, 2017 12:12 PM > *To:*

Re: Counter performance

Sending REQUEST_RESPONSE message to / > cassandra-01 [MessagingService-Outgoing-/ cassandra-01 ] | 2017-04-17 > 18:31:49.627000 | cassandra-05 | 3453 | cassandra-01 > > REQUEST_RESPONSE message received from / > cassandra-05 [Mes

Re: WriteTimeoutException with LWT after few milliseconds

Thanks, Jeff! As soon as I have some spare time I will try to reproduce and open a Jira for it. 2017-04-19 16:27 GMT+02:00 Jeff Jirsa <jji...@apache.org>: > > > On 2017-04-13 05:13 (-0700), benjamin roth <brs...@gmail.com> wrote: > > I found out that if the WTEs occur

Re: TRUNCATE on a disk almost full - possible?

Truncate needs no space. It just creates a hard link of all affected SSTables under the corresponding -SNAPSHOT dir (at least with default settings) and then removes the SSTables. Also this operation should be rather fast as it is mostly a file-deletion process with some metadata updates.

Re: hanging validation compaction

hausted: false and restarted again > > after that it worked ... but it also could be that it just worked by > accident after the last restart and is not related to my config changes > > On Thu, 2017-04-13 at 11:58 +0200, benjamin roth wrote: > > If you restart the server the same

Re: hanging validation compaction

java.util.concurrent.FutureTask.run(FutureTask.java:266) > java.util.concurrent.ThreadPoolExecutor.runWorker( > ThreadPoolExecutor.java:1142) > java.util.concurrent.ThreadPoolExecutor$Worker.run( > ThreadPoolExecutor.java:617) > org.apache.cassandra.concurrent.NamedThreadFactory. > lambda$threadLocalDeallocator$0(Na

Re: force processing of pending hinted handoffs

There is a nodetool command to resume hints. Maybe that helps? Am 13.04.2017 09:42 schrieb "Roland Otta" : > oh ... the operation is deprecated according to the docs ... > > > On Thu, 2017-04-13 at 07:40 +, Roland Otta wrote: > > i figured out that there is an mbean

Re: force processing of pending hinted handoffs

handoff handling in case it > hase been paused with the pausehandoff before. > i have tested it (resuming .. pausing & resuming) but it has no effect on > those old hints > > On Thu, 2017-04-13 at 10:27 +0200, benjamin roth wrote: > > There is a nodetool command to resume hints.

Re: hanging validation compaction

se/CASSANDRA > > On Thu, Apr 13, 2017 at 7:49 PM, benjamin roth <brs...@gmail.com> wrote: > > What I can tell you from that trace - given that this is the correct > thread and it really hangs there: > > The validation is stuck when reading from an SSTable. > Unfortunately

Re: hanging validation compaction

sstables for that > particular column_family > > is it possible to track down which sstable of that cf is affected or > should i upload all of them? > > > br, > roland > > > On Thu, 2017-04-13 at 13:57 +0200, benjamin roth wrote: > > I think thats a good r

Re: WriteTimeoutException with LWT after few milliseconds

gt; whats your consistency level for the insert? >> what if one ore more nodes are marked down and proper consistency cant be >> achieved? >> of course the error message does not indicate that problem (as it says >> its a timeout)... but in that case you would get an instant e

Re: hanging validation compaction

.run(Unknown Source) > java.lang.Thread.run(Thread.java:745) > > > br, > roland > > > On Thu, 2017-04-13 at 10:04 +0000, Roland Otta wrote: > > i did 2 restarts before which did not help > > after that i have set for testing purposes file_cache_size_in_mb: 0 and > buf

Re: scylladb

Why? Am 12.03.2017 07:02 schrieb "Jeff Jirsa" : > > > On 2017-03-10 09:57 (-0800), Rakesh Kumar wrote: > > Cassanda vs Scylla is a valid comparison because they both are > compatible. Scylla is a drop-in replacement for Cassandra. > > No, they aren't, and no, it isn't > > > > >

Re: scylladb

There is no reason to be angry. This is progress. This is the circle of live. It happens anywhere at any time. Am 12.03.2017 07:34 schrieb "Dor Laor" : > On Sat, Mar 11, 2017 at 10:02 PM, Jeff Jirsa wrote: > >> >> >> On 2017-03-10 09:57 (-0800), Rakesh

Re: scylladb

@Dor,Jeff: I think Jeff pointed out an important fact: You cannot stop CS, swap binaries and start Scylla. To be honest that was AFAIR the only "Oooh :(" I had when reading the Scylla "marketing material". If that worked it would be very valuable from both Scylla's and a users' point of view. As

Re: scylladb

Thanks a lot for your detailed explanation! I am very curious about the future development of Scylladb! Especially about mvs and lwt! Am 11.03.2017 02:05 schrieb "Dor Laor" : > On Fri, Mar 10, 2017 at 4:45 PM, Kant Kodali wrote: > >>

Re: Limit on number of keyspaces/tables

Why do you think 1 table consumes 1m?? Am 05.03.2017 20:36 schrieb "Vladimir Yudovin" : > Hi, > > there is no such hard limit, but each table consume at least 1M memory, so > 1000 tables takes at least 1G. > > Best regards, Vladimir Yudovin, > *Winguzone

Re: Limit on number of keyspaces/tables

No seriously. Am 05.03.2017 2:54 nachm. schrieb "Rakesh Kumar" : > > I ask back: what's your intention > > May be documenting the limitations of Cassandra to show Oracle is better > :-) > > Am 05.03.2017 11:58 schrieb "Lata Kannan"

Re: Limit on number of keyspaces/tables

I ask back: what's your intention Am 05.03.2017 11:58 schrieb "Lata Kannan" : > Hi > > I just wanted to check if there is any known limit to the number of > keyspaces one can create in a Cassandra cluster? Alternatively is there a > max on the number of tables that can be

Re: Non-zero nodes are marked as down after restarting cassandra process

You should always drain nodes before stopping the daemon whenever possible. This avoids commitlog replay on startup. This can take a while. But according to your description commit log replay seems not to be the cause. I once had a similar effect. Some nodes appeared down for some other nodes and

Re: Resources for fire drills

Could you specify it a little bit? There are really a lot of things that can go wrong. 2017-03-01 10:59 GMT+01:00 Malte Pickhan : > Hi Cassandra users, > > I am looking for some resources/guides for firedrill scenarios with apache > cassandra. > > Do you know anything

Re: Resources for fire drills

can exercise them with your team. > > Best > > > On 1 Mar 2017, at 11:01, benjamin roth <brs...@gmail.com> wrote: > > Could you specify it a little bit? There are really a lot of things that > can go wrong. > > 2017-03-01 10:59 GMT+01:00 Malte Pickhan <malte

Re: Resources for fire drills

the point. > > What I mean are some overview for basic scenarios for firedrills, so that > you can exercise them with your team. > > Best > > > On 1 Mar 2017, at 11:01, benjamin roth <brs...@gmail.com> wrote: > > Could you specify it a little bit? There are really a l

Re: Resources for fire drills

@Doc: http://cassandra.apache.org/doc/latest/ is built from the git repo. So you can add documentation in doc/source and submit a patch. I personally think that is not the very best place or way to build a knowledge DB but thats what we have. 2017-03-01 13:39 GMT+01:00 Malte Pickhan

Re: Can I do point in time recover using nodetool

I remember a very similar question on the list some months ago. The short answer is that there is no short answer. I'd recommend you search the mailing list archive for "backup" or "recover". 2017-03-08 10:17 GMT+01:00 Bhardwaj, Rahul : > Hi All, > > > > Is there any

Re: nodes are always out of sync

Tl;Dr: there are race conditions in a repair and it is not trivial to fix them. So we rather stay with these race conditions. Actually they don't really hurt. The worst case is that ranges are repaired that don't really need a repair. Am 01.04.2017 21:14 schrieb "Chris Lohfink"

Re: nodes are always out of sync

I think your way to communicate needs work. No one forces you to answer on questions. Am 01.04.2017 21:09 schrieb "daemeon reiydelle" : > What you are doing is correctly going to result in this, IF there is > substantial backlog/network/disk or whatever pressure. > > What do

Re: Corrupted commit log prevents Cassandra start

Hi Hannu, I remember there have been discussions about this in the past. Most probably there is already a JIRA for this. I roughly remember a consense like that: - Default behaviour should remain - It should be configurable to the needs and preferences of the DBA - It should at least spit out

Re: Cassandra seems slow when having many read operations

Apart from all that you can try to reduce the compression chunk size from the default 64kb to 16kb or even down to 4kb. This can help a lot if your read io on disk is very high and the page cache is not efficient. Am 21.07.2017 23:03 schrieb "Petrus Gomes" : > Thanks a lot to

Re: Cassandra seems slow when having many read operations

creased heap to 24GB. do you use cms or g1gc? > did you change any other parameters? > As for the chunk size, we found change 64kb to 16kb didn't make a > difference in low key cache rate environment > > > > On Fri, Jul 21, 2017 at 9:27 PM, benjamin roth <brs...@gmail.com>

Re: Is it possible to repair a single partition.

Then the partition is too big or has too many sstables that contain data for that partition so that the query times out. You can run a manual compaction on that table. That helped me several times. + I hope you are not trying to read that parition at once. Please use paging to query large

Re: Cassandra Cluster issues

Hm that question is like "My car does not start - whats the problem?". You have to monitor, monitor, monitor, monitor. I'd strongly advice to graph as many metrics as you can. Read them from the JMX interface and write them to a TSDB, visualize them e.g. with Grafana. Then read logs, trace your

<    1   2