Hi all,
Thanks for the responses, this was very helpful.
I don't know yet what the distribution of clicks and users will be, but I
expect to see a few users with an enormous amount of interactions and most
users having very few. The idea of doing some additional manual
partitioning, and then
Hi,
Ran into RPC timeout exception when execution a query that involve
secondary index of a Boolean column when for example the company has more
than 1k person.
select * from company where company_id= and isMale = true;
such extreme low cardinality of secondary index like the other docs
Note for anyone who accidentally or otherwise ends up with 2.1.3 in a situation
they cannot downgrade, feel free to look at
https://github.com/vast-engineering/cassandra/tree/vast-cassandra-2.1.3
https://github.com/vast-engineering/cassandra/tree/vast-cassandra-2.1.3
We sometimes make custom
Note that using static column(s) for the “head” value, and trailing TTLed
values behind is something we’re considering. Note this is especially nice if
your head state includes say a map which is updated by small deltas (individual
keys)
We have not yet studied the effect of static columns on
I would definitely wait for at least 2.1.4
On Mar 6, 2015, at 8:13 AM, Fredrik Larsson Stigbäck
fredrik.l.stigb...@sitevision.se wrote:
So no upgradeSSTables are required?
/Fredrik
6 mar 2015 kl. 15:11 skrev Carlos Rolo r...@pythian.com
mailto:r...@pythian.com:
I would not
What’s the recommended way of upgrading from 2.0.9 to 2.1.3?
Is upgradeSSTables required?
According to
http://www.datastax.com/documentation/upgrade/doc/upgrade/cassandra/upgradeC_c.html
http://www.datastax.com/documentation/upgrade/doc/upgrade/cassandra/upgradeC_c.html
it should be possible
I would not recommend an upgrade to 2.1.x for now. Do you have any specific
reason to upgrade?
For upgrading from 2.0.9 you can just do a direct upgrade.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant
Pythian - Love your data
rolo@pythian | Twitter: cjrolo | Linkedin:
So no upgradeSSTables are required?
/Fredrik
6 mar 2015 kl. 15:11 skrev Carlos Rolo r...@pythian.com:
I would not recommend an upgrade to 2.1.x for now. Do you have any specific
reason to upgrade?
For upgrading from 2.0.9 you can just do a direct upgrade.
Regards,
Carlos Juzarte
Hi there,
What is the best way to downgrade a C* 2.1.3 cluster to the stable 2.0.12?
I know it's not supported, but we are getting too many issues with the 2.1.x...
It is leading us to think that the best solution is to use the stable version.
Is there a safe way to do that?
Cheers,
Roni
AFAIK downgrading is not officially supported.
how much data do you have? If all possible I would dump all my data out and
bulk load them into the 2.0.x cluster. This is the only way I feel safe.
On Mar 6, 2015 5:55 AM, Roni Balthazar ronibaltha...@gmail.com wrote:
Hi there,
What is the best
well, StatusLogger.java started shown in cassandra
system.log, MessagingService.java also shown some stage (e.g. read,
mutation) dropped.
It's strange it only happen in this node but this type of message does not
shown in other node log file at the same time...
Jason
On Thu, Mar 5, 2015 at 4:26
I am using QUORUM
CQL
No SSDs (Anyway my IOPs is quite low so I dont think so it matters)
No compaction is running when I receive timeout
On Fri, Mar 6, 2015 at 12:35 AM, Carlos Rolo r...@pythian.com wrote:
What is the consistency level you are using?
Are you using Thrift or CQL?
Are you
Hi Roni,
We had the same problem and had to build a new, separate cluster. We read
from both clusters in the beginning and copied the data in the background
by paging over our data in the old 2.1.3 cluster. This allowed us to make
the downgrade seemless. Just watch out for 2.0.12's bug with
I want fo increase replication factor in my C* 2.1.3 cluster(rf chang from
2 to 3 for some keyspaces).
I read the doc of Updating the replication factor
http://www.datastax.com/documentation/cql/3.1/cql/cql_using/update_ks_rf_t.html
.
The step two is run the nodetool repair.But as I know nodetool
On Fri, Mar 6, 2015 at 6:25 AM, graham sanderson gra...@vast.com wrote:
I would definitely wait for at least 2.1.4
+1
https://engineering.eventbrite.com/what-version-of-cassandra-should-i-run/
=Rob
HI Jason;
The single node showing the anomaly is a hint that the problem is probably
local to a node (as you suspected).
- How many nodes do you have on the ring ?
- What is the activity when this occurs - reads / writes/ compactions ?
- Is there anything that is
What is the consistency level you are using?
Are you using Thrift or CQL?
Are you using SSDs?
Check if compactions are running when you get the timeouts.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant
Pythian - Love your data
rolo@pythian | Twitter: cjrolo | Linkedin:
17 matches
Mail list logo