Resolved comment discussions in the design document that are closed.
If there is no further feedback, I will start a voting thread tomorrow.
Thanks,
Sumanth
On Thu, Sep 2, 2021 at 6:54 AM Joshua McKenzie wrote:
> I'm +1 on where it currently stands after the revisions. Consider resolving
> out
I'm +1 on where it currently stands after the revisions. Consider resolving
out comment threads on the design doc that are closed so we can see if
there's any outstanding discussions from a high level?
~Josh
On Mon, Aug 30, 2021 at 1:14 AM Sumanth Pasupuleti <
sumanth.pasupuleti...@gmail.com> wro
+1. Made changes to the design document linked against the CEP to reflect
this feedback. Specifically, the following sections have been updated
* Operations to blacklist
* Blacklist information store
Thanks,
Sumanth
On Fri, Aug 27, 2021 at 7:57 AM Joshua McKenzie
wrote:
> I can see the case fo
I can see the case for all three:
* Deny both reads and writes to a partition (wide, heavily tombstones, too
many stables, etc) causing disruption to a replica set; don't want further
growth nor reads until operator intervention
* Deny reads but allow writing to rectify problems on a partition
(int
Thank you, Josh for the elaborate explanation of a potential scenario where
denylisting writes would make sense.
I, 100% agree that could benefit in a situation where we would want to deny
writes to a partition that we do not have much control on (which is true in
most situations) and such behavior
The design doc and CEP currently pass on blocklisting / denylisting writes
at this time. In the proposed new patch it states:
"Note: We do not want to blacklist writes since it is the reads that
primarily impact the performance when reading a bad partition, and we may
want writes to be allowed to “
Certainly. I'll take on distilling a high level view of the feature from
what Jon and I are working on to bring to this discussion.
On Tue, Aug 17, 2021 at 1:40 PM Sumanth Pasupuleti <
sumanth.pasupuleti...@gmail.com> wrote:
> +1 to collaborating on the patch, Josh. My 2 cents would be to contin
+1 to collaborating on the patch, Josh. My 2 cents would be to continue to
pursue this CEP in the community through Discuss and Vote phases and then
invest further on the patch (based on the Vote phase outcome), so we can
reflect any additional feedback we may gather from the community through
this
Sumanth,
Jon Meredith and I are recently working on an OSS patch of one of those "ad
hoc" implementations of this feature that's been running at scale for
awhile like Jirsa mentioned; sorry for not catching the discussion on
https://issues.apache.org/jira/browse/CASSANDRA-12106 and engaging earlie
Starting a discussion thread for CEP-13
https://cwiki.apache.org/confluence/display/CASSANDRA/CEP-13%3A+Denylisting+partitions
This CEP proposes adding a new feature to Cassandra to be able to denylist
partitions.
Looking forward to any feedback/ thoughts.
Thanks,
Sumanth
10 matches
Mail list logo
