[jira] [Updated] (CASSANDRA-21239) Synchronously publish changes to local gossip state following metadata updates

["Sam Tunnicliffe (Jira)" <ji...@apache.org>]

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

Sam Tunnicliffe updated CASSANDRA-21239:
----------------------------------------
    Attachment: ci_summary.html
                result_details.tar.gz

> Synchronously publish changes to local gossip state following metadata updates
> ------------------------------------------------------------------------------
>
>                 Key: CASSANDRA-21239
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-21239
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Cluster/Gossip, Transactional Cluster Metadata
>            Reporter: Sam Tunnicliffe
>            Assignee: Sam Tunnicliffe
>            Priority: Normal
>         Attachments: ci_summary.html, result_details.tar.gz
>
>
> Executing {{LegacyStateListener}} callbacks asynchronously, using {{ScheduledExecutors.optionalTasks}} can lead to gossip changes, specifically for {{SCHEMA_VERSION}} being processed out of order. While this is harmless for Cassandra internally, it can lead to inconsistencies between the schema versions reported in the {{system.local}} table and the {{system.peers_v2}} tables and that may be problematic for clients.
> There is no compelling reason for a {{ChangeListener}} implementation to be asynchronous , so we should just remove the {{Async}} interface.



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