yes correct, it doesn't work for the servers. trying to see if any had any
workaround for this issue? (may be changing the protocol version during the
upgrade time?)
On Fri, Jul 26, 2019 at 1:11 PM Durity, Sean R
wrote:
> This would handle client protocol, but not streaming protocol between
> no
Any one has Cheat Sheet for Unix based OS, Performance troubleshooting ?
This would handle client protocol, but not streaming protocol between nodes.
Sean Durity – Staff Systems Engineer, Cassandra
From: Alok Dwivedi
Sent: Friday, July 26, 2019 3:21 PM
To: user@cassandra.apache.org
Subject: Re: [EXTERNAL] Apache Cassandra upgrade path
Hi Sean
The recommended practi
Hi Sean
The recommended practice for upgrade is to explicitly control protocol
version in your application during upgrade process. Basically the protocol
version is negotiated on first connection and based on chance it can talk
to an already upgraded node first which means it will negotiate a highe
Thanks Sean,
In my use case all my clusters are multi DC, and I am trying my best effort
to upgrade ASAP, however there is a chance since all machines are VMs. Also
my key spaces are not uniform across DCs. some are replicated to all DCs
and some of them are just one DC, so I am worried there.
Is
What you have seen is totally expected. You can’t stream between different
major versions of Cassandra. Get the upgrade done, then worry about any down
hardware. If you are using DCs, upgrade one DC at a time, so that there is an
available environment in case of any disasters.
My advice, though
Hello,
I am trying to upgrade Apache Cassandra from 2.1.16 to 3.11.3, the regular
rolling upgrade process works fine without any issues.
However, I am running into an issue where if there is a node with older
version dies (hardware failure) and a new node comes up and tries to
bootstrap, it's fai
Hi,
To my knowledge there is no set date for 4.0, the community is
prioritizing QA over fast release which I think is great! Anytime
during Q4 is suggested. See the latest information from the dev mailing
list: https://lists.apache.org/thread.html/1a768d057d1af5a0f373c4c399a2
3e65cb04c61bbfff612634
Hi,
When Apache Cassandra 4.0 will release? Any specific time line? I am eagerly
waiting for audit log.
Regards,
-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassan
Hi,
This community is very helpful.
Looking for any pointers.
Anyone knows any opening in your team for Cassandra Admin skill in BayArea
/ Remote?
Please send me email .
Thanks
Krish
Hi,
did you also consider to “tame” your spark job by reducing it’s executors?
Probably the Job will have a longer runtime in exchange to reducing the stress
on the Cassandra cluster.
Regards
Christian
Von: "ZAIDI, ASAD A"
Antworten an: "user@cassandra.apache.org"
Datum: Donnerstag, 25. Juli
I fully agree to Jon here. We previously also used MV’s and major problems
popped up on decommissioning/commissioning nodes.
After replacing them by doing the MV’s job “manually” by code, we did not face
those issues anymore.
Regards,
Christian
Von: Jon Haddad
Antworten an: "user@cassandra.apa
In the mean time we opened traces and found that normal insert operations
does not have high latency. Delete operations have high latency. And all
deletes are range deletes. Is there any performance regression about range
deletes? Mean time of delete operations are 45 times higher than insert
opera
13 matches
Mail list logo
