You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Matt Fleming (Jira)" <ji...@apache.org> on 2021/09/16 12:30:00 UTC
[jira] [Updated] (CASSANDRA-16840) Close native transport port
before hint transfer during decommission
[ https://issues.apache.org/jira/browse/CASSANDRA-16840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matt Fleming updated CASSANDRA-16840:
-------------------------------------
Test and Documentation Plan: Patch available here, https://github.com/mfleming/cassandra/commit/ff07793d04823d39735190d930260bfeea6df59f
Status: Patch Available (was: In Progress)
> Close native transport port before hint transfer during decommission
> --------------------------------------------------------------------
>
> Key: CASSANDRA-16840
> URL: https://issues.apache.org/jira/browse/CASSANDRA-16840
> Project: Cassandra
> Issue Type: Improvement
> Components: Consistency/Hints
> Reporter: Matt Fleming
> Assignee: Matt Fleming
> Priority: Normal
> Fix For: 4.x
>
>
> New hints can be generated on a node when it's decommissioning which is a problem if the node has already started hint transfer because any hints that come in after the transfer has begun will remain on-disk and not be transferred to a peer.
> You can work around this problem by manually closing the native transport port before starting the decommission with {{nodetool disablebinary}} but it feels like something we might want to do automatically.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org