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

Hi Jeff,If increase the value, it will affect only newly created indexes. Will repair rebuilds old indexes with new , larger, size, or leave them with the same size?Best regards, Ilya Исходное сообщение Тема: Re: [EXTERNAL] Re: Make large partitons lighter on select without

Re: Ansible scripts for Cassandra to help with automation needs

> On Feb 13, 2019, at 9:51 PM, Kenneth Brotman > wrote: > > I want to generate a variety of Ansible scripts to share with the Apache > Cassandra community. I’ll put them in a Github repository. Just email me > offline what scripts would help the most. > > Does this exist already? I

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

We build an index on each partition as we write it - in 3.0 it’s a list that relates the clustering columns for a given partition key to a point in the file. When you read, we use that index to skip to the point at the beginning of your read. That 64k value is just a default that few people

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

Hello!increase column_index_size_in_kb for rarely index creations, am I correct?But will it be used in every read request, or column index for queries within a row only?Best regards, Ilya Исходное сообщение Тема: Re: [EXTERNAL] Re: Make large partitons lighter on select without

Ansible scripts for Cassandra to help with automation needs

I want to generate a variety of Ansible scripts to share with the Apache Cassandra community. I'll put them in a Github repository. Just email me offline what scripts would help the most. Does this exist already? I can't find it. Let me know if it does. If not, let's put it together

Re: How to upgrade logback dependency

On 2/13/19 2:30 AM, Oleksandr Shulgin wrote: > On Tue, Feb 12, 2019 at 7:02 PM Michael Shuler > wrote:  > > If you are not using the logback SocketServer and ServerSocketReceiver > components, the CVE doesn't affect your server with logback 1.1.3. > > >

Re: forgot to run nodetool cleanup

On Wed, Feb 13, 2019 at 7:47 AM Oleksandr Shulgin < oleksandr.shul...@zalando.de> wrote: > On Wed, Feb 13, 2019 at 4:40 PM Jeff Jirsa wrote: > >> Some people who add new hosts rebalance the ring afterward - that >> rebalancing can look a lot like a shrink. >> > > You mean by moving the tokens?

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

@all, thank you for your answers, Jeff, Thank you very much, will look into it. ср, 13 февр. 2019 г., 18:38 Jeff Jirsa jji...@gmail.com: > Cassandra-11206 (https://issues.apache.org/jira/browse/CASSANDRA-11206) > is in 3.11 and does have a few knobs to make this less painful > > You can also

Re: forgot to run nodetool cleanup

On Wed, Feb 13, 2019 at 4:40 PM Jeff Jirsa wrote: > Some people who add new hosts rebalance the ring afterward - that > rebalancing can look a lot like a shrink. > You mean by moving the tokens? That's only possible if one is not using vnodes, correct? I also believe, but don’t have time to

Re: forgot to run nodetool cleanup

Some people who add new hosts rebalance the ring afterward - that rebalancing can look a lot like a shrink. I also believe, but don’t have time to prove, that enough new hosts can eventually give you a range back (moving it all the way around the ring) - less likely but probably possible.

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

Cassandra-11206 (https://issues.apache.org/jira/browse/CASSANDRA-11206) is in 3.11 and does have a few knobs to make this less painful You can also increase the column index size from 64kb to something significantly higher to decrease the cost of those reads on the JVM (shifting cost to the

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

Agreed. It’s pretty close to impossible to administrate your way out of a data model that doesn’t play to Cassandra’s strengths. Which is true for other data storage technologies – you need to model the data the way that the engine is designed to work. Sean Durity From: DuyHai Doan Sent:

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

Plain answer is NO There is a slight hope that the JIRA https://issues.apache.org/jira/browse/CASSANDRA-9754 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 13, 2019 at 1:18 PM Vsevolod Filaretov wrote: > Hi

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

Hi all, The question. We have Cassandra 3.11.1 with really heavy primary partitions: cfhistograms 95%% is 130+ mb, 95%% cell count is 3.3mln and higher, 98%% partition size is 220+ mb sometimes partitions are 1+ gb. We have regular problems with node lockdowns leading to read request timeouts

Re: forgot to run nodetool cleanup

On Wed, Feb 13, 2019 at 5:31 AM Jeff Jirsa wrote: > The most likely result of not running cleanup is wasted disk space. > > The second most likely result is resurrecting deleted data if you do a > second range movement (expansion, shrink, etc). > > If this is bad for you, you should run cleanup

Re: How to upgrade logback dependency

On Tue, Feb 12, 2019 at 7:02 PM Michael Shuler wrote: > If you are not using the logback SocketServer and ServerSocketReceiver > components, the CVE doesn't affect your server with logback 1.1.3. > So the idea is that as long as logback.xml doesn't configure any of the above, we are fine with