Re: About the relationship between the sstable compaction and the read path

Thanks. Let me clarify my questions more. 1) For memtable, if the selected columns (assuming they are in simple types) could be found in memtable only, why bother to search sstables then? In leveldb and rocksdb, they would stop consulting sstables if the memtable already fulfill the query. 2)

Re: Authenticate cassandra-stress with cqlshrc

Yep, cassandra-stress doesn’t attempt to use the cqlshrc file. Seems to me it could be convenient so might make a nice contribution to the project. Cheers Ben --- *Ben Slater* *Chief Product Officer*

Re: Authenticate cassandra-stress with cqlshrc

Yes, my cluster is set up to authenticate using PasswordAuthentication(host, user and password are stored in cqlshrc). When I try to run Cassandra-stress without providing user & password on command line, it through authentication error. I expect Cassandra-stress to read cqlshrc file and

Re: Authenticate cassandra-stress with cqlshrc

Is your cluster set up to require authentication? I’m a bit unclear about whether you’re trying to connect without passing a user name and password at all (which should just work as the default) or if you’re looking for some mechanism other than the command line to pass the user name / password

Authenticate cassandra-stress with cqlshrc

I'm trying to connect cassandra-stress 3.11.0 without providing user and password option on the comman line. It doesn't seems to be using cqlshrc. Any suggestions please? -Arvinder

Re: How seed nodes are working and how to upgrade/replace them?

I've done some gossip simulations in the past and found virtually no difference in the time it takes for messages to propagate in almost any sized cluster. IIRC it always converges by 17 iterations. Thus, I completely agree with Jeff's comment here. If you aren't pushing 800-1000 nodes, it's

Re: How seed nodes are working and how to upgrade/replace them?

On Tue, Jan 8, 2019 at 8:19 AM Jonathan Ballet wrote: > Hi Jeff, > > thanks for answering to most of my points! > From the reloadseeds' ticket, I followed to > https://issues.apache.org/jira/browse/CASSANDRA-3829 which was very > instructive, although a bit old. > > > On Mon, 7 Jan 2019 at

Re: How seed nodes are working and how to upgrade/replace them?

Given Consul's popularity, seems like someone could make an argument that we should be shipping a consul-aware seed provider. On Tue, Jan 8, 2019 at 7:39 AM Jonathan Ballet wrote: > On Mon, 7 Jan 2019 at 16:51, Oleksandr Shulgin < > oleksandr.shul...@zalando.de> wrote: > >> On Mon, Jan 7, 2019

Re: How seed nodes are working and how to upgrade/replace them?

Hi Jeff, thanks for answering to most of my points! >From the reloadseeds' ticket, I followed to https://issues.apache.org/jira/browse/CASSANDRA-3829 which was very instructive, although a bit old. On Mon, 7 Jan 2019 at 17:23, Jeff Jirsa wrote: > > On Jan 7, 2019, at 6:37 AM, Jonathan Ballet

Re: About the relationship between the sstable compaction and the read path

First: Compaction controls how sstables are combined but not how they’re read. The read path (with one tiny exception) doesn’t know or care which compaction strategy you’re using. A few more notes inline. > On Jan 8, 2019, at 3:04 AM, Jinhua Luo wrote: > > Hi All, > > The compaction

Re: How seed nodes are working and how to upgrade/replace them?

On Mon, 7 Jan 2019 at 16:51, Oleksandr Shulgin wrote: > On Mon, Jan 7, 2019 at 3:37 PM Jonathan Ballet wrote: > >> >> I'm working on how we could improve the upgrades of our servers and how >> to replace them completely (new instance with a new IP address). >> What I would like to do is to

About the relationship between the sstable compaction and the read path

Hi All, The compaction would organize the sstables, e.g. with LCS, the sstables would be categorized into levels, and the read path should read sstables level by level until the read is fulfilled, correct? For STCS, it would search sstables in buckets from smallest to largest? What about other