[jira] [Assigned] (CASSANDRA-19158) Reuse native transport-driven futures in Debounce

["Alex Petrov (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/CASSANDRA-19158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alex Petrov reassigned CASSANDRA-19158:
---------------------------------------

    Assignee: Alex Petrov

> Reuse native transport-driven futures in Debounce
> -------------------------------------------------
>
>                 Key: CASSANDRA-19158
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19158
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Alex Petrov
>            Assignee: Alex Petrov
>            Priority: Normal
>
> Currently, we create a future in Debounce, then create one more future in RemoteProcessor#sendWithCallback. This is further exacerbated by chaining calls, when we first attempt to catch up from peer, and then from CMS.
> First of all, we should always only use a native transport timeout driven futures returned from sendWithCallback, since they implement reasonable retries under the hood, and are easy to bulk-configure (ie you can simply change timeout in yaml and have all futures change their behaviour).
> Second, we should _chain_ futures and use map or andThen for fallback operations such as trying to catch up from CMS after an unsuccesful attemp to catch up from peer.
> This should significantly simplify the code and number of blocked/waiting threads.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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