> As the repair is only guaranteed for a majority of replicas, I assume I
can discover somewhere which replicas are up to date like this?
I’m not quite sure what you mean. Do you mean which nodes have participated in
a paxos repair? This information isn’t maintained, but anyway would not imply
t
I think you were correct to start a DISCUSS thread, Bowen. You should not start
a vote until you have first established if there is consensus.
Also, I agree with the proposal.
From: Bowen Song
Date: Saturday, 4 December 2021 at 23:12
To: dev@cassandra.apache.org
Subject: Re: [DISCUSS] Disablin
Hmm.. It's too late to change that. I opened it as "DISCUSS" because I
was not sure if the information in it is enough for people to vote on
it. There's clearly a lot more can be asked or discussed. For example
the change will also stop the "To unsubscribe, ..." footer being
appended to some em
Could someone elaborate on this section
*Paxos Repair*
We will introduce a new repair mechanism, that can be run with or without
regular repair. This mechanism will:
- Track, per-replica, transactions that have been witnessed as initiated
but have not been seen to complete
- For a
> What's your opinion on this? Do you support or oppose disabling the
> MIME-part filtering on the Cassandra-dev mailing list?
+1
(nit: am thinking the thread should have had a [VOTE] prefix, since you are
calling out for consensus)
+1 (nb) from me.
I have always wondered why the signatures were broken. That JIRA thread is very
enlightening on how those email features work :).
> On Dec 4, 2021, at 11:18 AM, C. Scott Andreas wrote:
>
> +1, this would be great to have fixed. Thanks for talking with Infra about
> this, Bow
+1, this would be great to have fixed. Thanks for talking with Infra about
this, Bowen.
> On Dec 4, 2021, at 9:16 AM, Bowen Song wrote:
>
> Hello,
>
>
> Currently this mailing list has MIME-part filtering turned on, which will
> results in "From:" address munging (appending ".INVALID" to th
Hello,
Currently this mailing list has MIME-part filtering turned on, which
will results in "From:" address munging (appending ".INVALID" to the
sender's email address) for domains enforcing strict DMARC rules, such
as apple.com, zoho.com and all Yahoo.** domains. This behaviour may
cause so
After some offline collab, here's where this thread has landed on a
proposal to change our processes to incrementally improve our processes and
hopefully stabilize the state of CI longer term:
Link:
https://docs.google.com/document/d/1tJ-0K7d6PIStSbNFOfynXsD9RRDaMgqCu96U4O-RT84/edit#bookmark=id.16
