Safe read request timeout value

Good time of day everyone, I've got a question on timeouts setting practice. I've got a 4-node cluster with only a handful of users, constant data inserts and very large partitions (up to 450+mb, which is 4 times larger than general cassandra manuals recommend). Data is held on hdd. What are

[no subject]

Good time of day everyone, I've got three questions on Cassandra paging mechanics and cluster usage regulation. 1) Am I correct to assume that the larger page size some user session has set - the larger portion of cluster/coordinator node resources will be hogged by the corresponding session?

Re:

Kurt, thank you very much for your answer! Your remark on GC totally changed my thoughts on cassandra resources usage. So.. more questions to the respective audience underway. What is generally considered as 1) "too large" page size, 2)"large" page size 3) "normal conditions" page size? How

Setting up rerouting java/python driver read requests from unresponsive nodes to good ones

, to the up and running one (dynamically switch to other coordinator node from the dead one)? If the answer is no, what could be my alternatives? Thank you all in advance, Vsevolod Filaretov.

Cassandra node RAM amount vs data-per-node/total data?

What are general community and/or your personal experience viewpoints on cassandra node RAM amount vs data stored per node question? Thank you very much. Best regards, Vsevolod.

Re: Cassandra recommended server uptime?

not need regular reboots for Cassandra’s sake, but you should be > regularly patching your servers > > > -- > Jeff Jirsa > > > > On Jul 17, 2018, at 2:09 AM, Vsevolod Filaretov > wrote: > > > > Good time of day everyone; > > > > Does Cassandra h

Cassandra recommended server uptime?

Good time of day everyone; Does Cassandra have a "recommended uptime"? I.e., does regular Cassandra node reboots help anything? Are periodical node reboots recommended for general system stability? Best regards, Vsevolod.

Re: Cassandra recommended server uptime?

ths/years without > rebooting. > It is better to monitor your nodes and if you find anything abnormal a > restart can help. > > -- > SIMON FONTANA OSCARSSON > Software Developer > > Ericsson > Ölandsgatan 1 > 37133 Karlskrona, Sweden > simon.fontana.oscars...@ericsson

Re: Cassandra node RAM amount vs data-per-node/total data?

n to keep in > memory in terms of key / row cache. For my uses, no less than 64GB if not > more ~ 128GB. The lowest I’ve gone is 16GB but that’s for dev purposes > only. > > -- > Rahul Singh > rahul.si...@anant.us > https://www.anant.us/datastax > > Anant Corporation >

Common knowledge on C* heap size/file _cache_size_in_mb/other RAM usage parameters

What are general community guidelines on setting up C* heap size, file_cache_size_in_mb, offheap space usage and other RAM usage settings? Are there any general guidelines like "if your total data size per node is X/median/max partition size is Y, your RAM usage settings better be Z or things

Java driver speculative requests: exactly 90 seconds read request wait time if speculative requests enabled.

a bit out of ideas where to look. Where the problem might be? Even "lame"/"easy" hypotheses are welcome, because my vision actually might be blurred with the search. Thank you all very much in advance. Best regards, Vsevolod Filaretov.

New node insertion methods

with tens of Cassandra nodes perform insertion/extraction of new/failed nodes? What's the usual routine in case you have 20+ nodes, and need to decommission 4 nodes and insert 4 new ones instead? Links to blog posts or mail threads much appreciated! Thank you all in advance, Vsevolod Filaretov.

Make large partitons lighter on select without changing primary partition formation.

under read requests load. Changing primary partition key structure is out of question. Are there any sharding techniques available to dilute partitions at level lower than 'select' requests to make read performance better? Without changing read requests syntax? Thank you all in advance, Vsevolod

Re: [EXTERNAL] Re: Make large partitons lighter on select without changing primary partition formation.

cZTtVYWDDvyLkh8IaQ=YH5vXIEwCC-CMZNOyNJCAHTeso6N1JZHkgoolKHKQjE=KjhchSZTtYYl60nfet6WB1fQd-Ph2P-YOD-GQzUJj2o=> > gets into 4.0 release > > > > But right now, there seems to be few interest in this ticket, the last > comment 23/Feb/2017 old ... > > > > > > On Wed, Feb

Select in allow filtering stalls whole cluster. How to prevent such behavior?

subset of C* nodes and not by all of them, as per connection consistency/table replication settings, in case. 2) Is it possible to forbid ALLOW FILTERING flag for given users/groups? Thank you all very much in advance, Vsevolod Filaretov.