[prev in list] [next in list] [prev in thread] [next in thread] 

List:       cassandra-dev
Subject:    Re: [DISCUSS] CASSANDRA-16840 - Close native transport port before hint transfer during decommission
From:       Matt Fleming <matt () codeblueprint ! co ! uk>
Date:       2021-09-16 12:32:39
Message-ID: 20210916123239.GA8 () codeblueprint ! co ! uk
[Download RAW message or body]

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 <matt@codeblueprint.co.uk>
> 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-unsubscribe@cassandra.apache.org
> > For additional commands, e-mail: dev-help@cassandra.apache.org
> >
> >

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@cassandra.apache.org
For additional commands, e-mail: dev-help@cassandra.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]