[jira] [Updated] (CASSANDRA-13569) Schedule schema pulls just once per endpoint

["Stefan Podkowinski (JIRA)" <ji...@apache.org>]

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

Stefan Podkowinski updated CASSANDRA-13569:
-------------------------------------------
    Status: Open  (was: Patch Available)

> Schedule schema pulls just once per endpoint
> --------------------------------------------
>
>                 Key: CASSANDRA-13569
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13569
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Distributed Metadata
>            Reporter: Stefan Podkowinski
>            Assignee: Stefan Podkowinski
>            Priority: Major
>             Fix For: 3.0.x, 3.11.x, 4.x
>
>
> Schema mismatches detected through gossip will get resolved by calling {{MigrationManager.maybeScheduleSchemaPull}}. This method may decide to schedule execution of {{MigrationTask}}, but only after using a {{MIGRATION_DELAY_IN_MS = 60000}} delay (for reasons unclear to me). Meanwhile, as long as the migration task hasn't been executed, we'll continue to have schema mismatches reported by gossip and will have corresponding {{maybeScheduleSchemaPull}} calls, which will schedule further tasks with the mentioned delay. Some local testing shows that dozens of tasks for the same endpoint will eventually be executed and causing the same, stormy behavior for this very endpoints.
> My proposal would be to simply not schedule new tasks for the same endpoint, in case we still have pending tasks waiting for execution after {{MIGRATION_DELAY_IN_MS}}.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

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