That sounds like a possibility to me on the surface.
Kind Regards,
Brandon
On Fri, Dec 20, 2024 at 8:42 AM Paul Chandler wrote:
>
> Hi Brandon,
>
> That sounds good. Will that fix be in 4.1, as it is the old nodes that don’t
> transmit the hints?
>
> Thanks
>
> Paul
>
> > On 20 Dec 2024, at 13:
Hi Brandon,
That sounds good. Will that fix be in 4.1, as it is the old nodes that don’t
transmit the hints?
Thanks
Paul
> On 20 Dec 2024, at 13:41, Brandon Williams wrote:
>
> I think after a discussion on #cassandra-dev yesterday, we are going
> to remove the requirement for schema agree
I think after a discussion on #cassandra-dev yesterday, we are going
to remove the requirement 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
Hi Brandon,
I am not sure which part changes after CASSANDRA-20118, there is still the
system mismatch going to CASSANDRA_4 caused by the change in
system.compaction_history, and going to UPGRADING, this is caused by the 2
different sstable formats, so nothing that CASSANDRA-20118 fixes.
So w
On Thu, Dec 19, 2024 at 4:11 AM Paul Chandler wrote:
> C*4 -> CASSANDRA_4 : There is a schema mismatch, and hints are not sent from
> C*4 node to C*5 nodes.
> CASSANDRA_4 -> UPGRADING: Repairs are not possible and Nodes cannot be added
> or replaced.
> UPGRADING-> NONE: No issues.
I'll note thi
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
