Re: cqlsh problem

why cassandra using tcp6 for 9042 port like : tcp6 0 0 0.0.0.0:9042:::*LISTEN would this be the problem 2016-03-30 11:34 GMT+08:00 joseph gao : > still have not fixed it . cqlsh: error: no such option: --connect-timeout > cqlsh

Inconsistent query results and node state

We have encountered a query inconsistency problem wherein the following query returns different results sporadically with invalid values for a timestamp field looking like the field is uninitialized (a zero timestamp) in the query results. Attempts to repair and compact have not changed the

Re: cqlsh problem

still have not fixed it . cqlsh: error: no such option: --connect-timeout cqlsh version 5.0.1 2016-03-25 16:46 GMT+08:00 Alain RODRIGUEZ : > Hi Joseph. > > As I can't reproduce here, I believe you are having network issue of some > kind. > > MacBook-Pro:~ alain$ cqlsh

Re: How is the coordinator node in LOCAL_QUORUM chosen?

How this works is probably documented in greater detail at the link I provided before than I can do justice to here. TokenAware uses its configured child strategy to determine node locality. DCAwareRoundRobin uses a configuration property, or if all of its seed nodes are in the same DC it assumes

Re: Solr and vnodes anyone?

IIRC in DSE 4.6 using vnodes is basically always a bad idea in your Solr datacenter. The overhead was more than you could reasonably want to pay unless your vnode count was low enough that you lost all the advantage. Around 4.7 there were significant performance improvements for vnodes in DSE

Re: Does saveToCassandra work with Cassandra Lucene plugin ?

Hi Eduardo, It works. I think SPARKC-332 is fine. Thanks, Cleosson From: Eduardo Alonso Sent: Tuesday, March 29, 2016 11:39 AM To: user@cassandra.apache.org Subject: Re: Does

Re: Drop and Add column with different datatype in Cassandra

On Tue, Mar 29, 2016 at 10:31 AM, Bhupendra Baraiya < bhupendra.bara...@continuum.net> wrote: > Does it mean Cassandra does not allow adding of the same column in the > Table even though it does not exists in the Table > As the error message says, you can't re-add a *collection* column with the

Drop and Add column with different datatype in Cassandra

Hi , I am using Cassandra 3.0.4 I am using a Table called User which has a column last_login with Map datatype . I dropped the column using the syntax Alter Table User Drop last_login; I dropped the column from table and recreated it with a nested datatype last_login

Re: Does saveToCassandra work with Cassandra Lucene plugin ?

Hi, It seems that the problem is caused by a problem in the Cassandra Spark driver, and not in the plugin. Since CASSANDRA-10217 Cassandra 3.x per-row indexes don't require to be created on a fake column anymore. Thus, from Cassandra 3.x

Re: How is the coordinator node in LOCAL_QUORUM chosen?

Thanks for the explanation. My question is * How the client driver would determine which cassandra node is considered "local". Is it auto discovered (if so, how?) or manually specified somewhere? * Whether local_xxx consistencies always fail when a partition is not replicated in the local DC,

Re: Acceptable repair time

IIRC when we switched to LCS and ran the first full repair with 250GB/RF=3, it took at least 12 hours for the repair to finish, then another 3+ days for all the compaction to catch up. I called it "the big bang of LCS". Since then we've been running nightly incremental repair. For me as long as

Re: Does saveToCassandra work with Cassandra Lucene plugin ?

Hi Eduardo, As I was not sure that is a bug, I preferred to send the e-mail to list first. It could be something was done wrong. The versions are: * Spark 1.6.0 * Cassandra 3.0.3 * Lucene plugin 3.0.3.1 I opened the bug. The link

Re: Acceptable repair time

I would really like to know the answer for above because on some nodes repair takes almost 4 days for us :(. On Tue, Mar 29, 2016 at 8:34 AM, Jack Krupansky wrote: > Someone recently asked me for advice when their repair time was 2-3 days. > I thought that was

Re: Does saveToCassandra work with Cassandra Lucene plugin ?

Hi Cleosson Jose, First of all, if you think this is a caused by a cassandra-lucene-index bug, this user list is not the best way to report it. Please use github issues for this.

RE: How many nodes do we require

Because if you lose a node you have chances to lose some data forever if it was not yet replicated. -- Jacques-Henri Berthemet From: Jonathan Haddad [mailto:j...@jonhaddad.com] Sent: vendredi 25 mars 2016 19:37 To: user@cassandra.apache.org Subject: Re: How many nodes do we require Why would