Did you run any alter command during upgrade.?
No need to run drain before running upgrade sstable.
Regards
Manish
On Fri, Jun 26, 2020 at 9:48 PM Meenakshi Subramanyam
wrote:
> A quick question on the same topic, we are upgrading from 3.11.1 to
> 3.11.6. We had a schema mismatch after
A quick question on the same topic, we are upgrading from 3.11.1 to 3.11.6.
We had a schema mismatch after upgrading one node. RR did ont fix it and we
had to remove that node. have anyone faced this issue ?
Also Do we need to do a nodetool drain before running upgrade sstables.
Meena
On Wed,
Thank you!
The 2nd link you sent is very very good description! I recommend for
others too (who might run into this question via mail archive search
later...)
In my opinion it explains the entire problem space regarding how LWTs
are working while also putting them into the context of
You are correct. Lightweight transactions perform a read-before-write [1].
The read phase is performed with a serial consistency which requires a
quorum of nodes in the local DC (LOCAL_SERIAL) or across the whole cluster (
SERIAL) [2].
Quorum of 2 nodes is 2 nodes so RF=2 cannot tolerate a node
Ah yeah forgot to mention - I am using Cassandra 4.0-alpha4
Attila Wind
http://www.linkedin.com/in/attilaw
Mobile: +49 176 43556932
26.06.2020 08:06 keltezéssel, Attila Wind írta:
Hey guys,
Recently I ran into an interesting situation (by trying to add
optimistic locking strategy to one
Hey guys,
Recently I ran into an interesting situation (by trying to add
optimistic locking strategy to one of the tables)
Which lead me eventually to the following observation. Can you confirm
(or argue) this is correct when I am saying:
"It is not possible to use conditional queries with
