Hi All,
I have 18 node cluster across 3 dc , if i tey to run incremental repair on
singke node it takes forever sometome 45 to 1hr and sometime times out ..so
i started running "nodetool repair -dc dc1" for each dc one by one ..which
works fine ..do we have an better way to handle this?
I am
Pretty sure Ben meant that datastax produces DSE, not Cassandra, and since the
questions specifically mentions DSE in the subject (implying that the user is
going to be running either solr or spark within DSE to talk to cassandra),
Ben’s recommendation seems quite reasonable to me.
--
Jeff
Ben,
1. I don't see anything in this thread that is DSE specific, so I think it
belongs here.
2. Careful when you say that Datastax produces Cassandra. Cassandra is a
product of Apache Software Foundation, and no one else. You, Ben, should be
very well aware of this, to avoid further trademark
May see more isolation for our atomic operations with tickets like (for
example) https://issues.apache.org/jira/browse/CASSANDRA-7056
I don't know of any foreign key tickets off the top of my head, and I'm
almost positive nobody plans on working on that type of concept soon.
On Thu, Apr 12,
As mongodb is coming up acid compliance , do we see cassnadra bringung this
to table ? Also one brimgs in this , how it will compensate on performance
and other factors? Also any chance to bringe in relational constraints and
foreign key like cockroach db ?
Will driver upgrade is required if i move to 3.11.2 from 3.1.0? 3.x drivers
should work right?
On Thursday, April 12, 2018, Carlos Rolo wrote:
> Thanks for the heads-up. I will update the post.
>
> Regards,
>
> Carlos Juzarte Rolo
> Cassandra Consultant / Datastax Certified
Folks this is the user list for Apache Cassandra. I would suggest
redirecting the question to Datastax the commercial entity that produces
the software.
On Thu, Apr 12, 2018 at 9:51 AM vincent gromakowski <
vincent.gromakow...@gmail.com> wrote:
> Best practise is to use a dedicated DC for
Hi All,
In the doc:
https://docs.datastax.com/en/cassandra/3.0/cassandra/dml/dmlAboutDeletes.html
It said "When an unresponsive node recovers, Cassandra uses hinted
handoff to replay the database mutationsthe node missed while it was
down. Cassandra does not replay a mutation for a tombstoned
Best practise is to use a dedicated DC for analytics separated from the hot
DC.
Le jeu. 12 avr. 2018 à 15:45, sha p a écrit :
> Got it.
> Thank you so for your detailed explanation.
>
> Regards,
> Shyam
>
> On Thu, 12 Apr 2018, 17:37 Evelyn Smith,
Got it.
Thank you so for your detailed explanation.
Regards,
Shyam
On Thu, 12 Apr 2018, 17:37 Evelyn Smith, wrote:
> Cassandra tends to be used in a lot of web applications. It’s loads are
> more natural and evenly distributed. Like people logging on throughout the
> day.
Cassandra tends to be used in a lot of web applications. It’s loads are more
natural and evenly distributed. Like people logging on throughout the day. And
people operating it tend to be latency sensitive.
Spark on the other hand will try and complete it’s tasks as quickly as
possible. This
Thanks for the heads-up. I will update the post.
Regards,
Carlos Juzarte Rolo
Cassandra Consultant / Datastax Certified Architect / Cassandra MVP
Pythian - Love your data
rolo@pythian | Twitter: @cjrolo | Skype: cjr2k3 | Linkedin:
*linkedin.com/in/carlosjuzarterolo
Evelyn,
Can you please elaborate on below
Spark is notorious for causing latency spikes in Cassandra which is not
great if you are are sensitive to that.
On Thu, 12 Apr 2018, 10:46 Evelyn Smith, wrote:
> Are you building a search engine -> Solr
> Are you building an
13 matches
Mail list logo