Hint transfer during decommission

Hey friends, I'm looking for some feedback on whether what's been proposed in CASSANDRA-17808 is reasonable. To summarize... 1.) We continue to transfer hints by default during decommission, but at a higher rate. We could, for instance, stop

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 > reali

Re: [DISCUSS] CASSANDRA-16840 - Close native transport port before hint transfer during decommission

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 work

[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 transferre