[DISCUSS] CASSANDRA-16840 - Close native transport port before hint transfer during decommission
Hi, With the way that hint transfer currently works during decommission, it's possible to leave hints on the disk of the decommissioning node if those hints are generated after the decommission begins. I'd like to discuss automatically closing the native transport port before hints are transferred to peers during the decommission process to prevent this from happening. While it's possible to manually prevent this problem today if an operator runs "nodetool disablebinary" before starting the decom, I think the default behaviour is surprising enough that doing it automatically makes more sense. Thanks, Matt - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [DISCUSS] CASSANDRA-16840 - Close native transport port before hint transfer during decommission
Thanks Jeff. Since no one has objected I've submitted a patch to this jira ticket for review. On Tue, 10 Aug, at 01:27:55PM, Jeff Jirsa wrote: > The hint behavior aside, stopping native protocol once you begin a decom > seems like something most people would benefit from, even if they dont > realize that's what they want to happen. > > > > On Tue, Aug 10, 2021 at 12:53 PM Matt Fleming > wrote: > > > Hi, > > > > With the way that hint transfer currently works during decommission, > > it's possible to leave hints on the disk of the decommissioning node if > > those hints are generated after the decommission begins. > > > > I'd like to discuss automatically closing the native transport port > > before hints are transferred to peers during the decommission process to > > prevent this from happening. > > > > While it's possible to manually prevent this problem today if an > > operator runs "nodetool disablebinary" before starting the decom, I > > think the default behaviour is surprising enough that doing it > > automatically makes more sense. > > > > Thanks, > > Matt > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org > > For additional commands, e-mail: dev-h...@cassandra.apache.org > > > > - To unsubscribe, e-mail: dev-unsubscr...@cassandra.apache.org For additional commands, e-mail: dev-h...@cassandra.apache.org
Re: [VOTE] Release Apache Cassandra 4.1.0 GA
Me and Marianne are also still chasing a performance issue with Paxos v2 when compared with v1. We see way more contention on v2 for a LOCAL_SERIALIZABLE workload that writes/reads to only 100 partitions (v2 performs better for higher partition counts). We're still investigating what's going on. Should that be a -1 vote? I'm not sure :) On Mon, 5 Dec 2022 at 11:37, Benedict wrote: > -0 > > CASSANDRA-18086 should probably be fixed and merged first, as Paxos v2 > will be unlikely to work well for users without it. Either that or we need > to update NEWS.txt to mention it. > > On 5 Dec 2022, at 11:01, Aleksey Yeshchenko wrote: > > +1 > > On 5 Dec 2022, at 10:17, Benjamin Lerer wrote: > > +1 > > Le lun. 5 déc. 2022 à 11:02, Berenguer Blasi a > écrit : > >> +1 >> On 5/12/22 10:53, guo Maxwell wrote: >> >> +1 >> >> Mick Semb Wever 于2022年12月5日 周一下午5:33写道： >> >>> >>> Proposing the test build of Cassandra 4.1.0 GA for release. >>> >>> sha1: b807f97b37933fac251020dbd949ee8ef245b158 >>> Git: >>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1.0-tentative >>> Maven Artifacts: >>> https://repository.apache.org/content/repositories/orgapachecassandra-1281/org/apache/cassandra/cassandra-all/4.1.0/ >>> >>> The Source and Build Artifacts, and the Debian and RPM packages and >>> repositories, are available here: >>> https://dist.apache.org/repos/dist/dev/cassandra/4.1.0/ >>> >>> The vote will be open for 72 hours (longer if needed). Everyone who has >>> tested the build is invited to vote. Votes by PMC members are considered >>> binding. A vote passes if there are at least three binding +1s and no -1's. >>> >>> [1]: CHANGES.txt: >>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.1.0-tentative >>> [2]: NEWS.txt: >>> https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.1.0-tentative >>> >> -- >> you are the apple of my eye ! >> >> >
Re: [VOTE] Release Apache Cassandra 4.1.0 (take2)
Me and Marianne finished running all the tests for Paxos V2 with the bug fixes from CASSANDRA-18086 and the results for the 100 partitions are definitely better than V1. For the larger partitions (1000, 1), the results for V2 are comparable and overall V2 did not have any performance regression. +1 (non binding) On Wed, 7 Dec 2022 at 21:41, Mick Semb Wever wrote: > > Proposing the (second) test build of Cassandra 4.1.0 for release. > > sha1: f9e033f519c14596da4dc954875756a69aea4e78 > Git: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=shortlog;h=refs/tags/4.1.0-tentative > Maven Artifacts: > https://repository.apache.org/content/repositories/orgapachecassandra-1282/org/apache/cassandra/cassandra-all/4.1.0/ > > The Source and Build Artifacts, and the Debian and RPM packages and > repositories, are available here: > https://dist.apache.org/repos/dist/dev/cassandra/4.1.0/ > > The vote will be open for 96 hours (longer if needed). Everyone who has > tested the build is invited to vote. Votes by PMC members are considered > binding. A vote passes if there are at least three binding +1s and no -1's. > > [1]: CHANGES.txt: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=CHANGES.txt;hb=refs/tags/4.1.0-tentative > [2]: NEWS.txt: > https://gitbox.apache.org/repos/asf?p=cassandra.git;a=blob_plain;f=NEWS.txt;hb=refs/tags/4.1.0-tentative >
