t for schema agreement to deliver hints, as
> suggested by Jeff Jirsa.
>
> Kind Regards,
> Brandon
>
> On Thu, Dec 19, 2024 at 7:43 AM Paul Chandler wrote:
>>
>> Hi Brandon,
>>
>> I am not sure which part changes after CASSANDRA-20118, there is still the
while CASSANDRA-20118 improves things, it does not fix these specific
issues, unless I have missed something?
> On 19 Dec 2024, at 12:17, Brandon Williams wrote:
>
> On Thu, Dec 19, 2024 at 4:11 AM Paul Chandler wrote:
>> C*4 -> CASSANDRA_4 : There is a schema mismatch, and
All,
As suggested by Scott Andreas I am bringing this discussion to the dev mailing
list.
A couple of days ago I posted a question on the user mailing list [1] about the
storage compatibility modes and whether you can go straight to SCM (NONE) from
Cassandra 4.
I am currently do some presenta
I think there is a danger that when in comes to the next upgrade cycle there
could be production clusters still running in CASSANDRA_4 mode, as the
operators haven’t realised they need to move through the SCM levels. The
default setting for a new cluster is CASSANDRA_4 and unless a new operator
Hi All,
I raised a Jira bug last week (
https://issues.apache.org/jira/browse/CASSANDRA-20118 )
We are finding that hints are not being transmitted during the first step of
the upgrade process from C*4 to C*5, this seems to be due to the schema
mismatch. Full details are in the bug report.
Ca
the Epic CASSANDRA-19055 or create them
standalone?
Thanks
Paul Chandler
Hi Greg,
Andy is talking about Cassandra datacenters, which can easily be co located in
the same physical datacenter.
Paul
> On 15 Dec 2020, at 12:10, Greg Oliver wrote:
>
> That's great in theory, but what if your customer is a national government
> (they require their data to remain within
