cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Podkowinski (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CASSANDRA-13569) Schedule schema pulls just once per endpoint
Date Fri, 02 Jun 2017 10:32:04 GMT
Stefan Podkowinski created CASSANDRA-13569:
----------------------------------------------

             Summary: Schedule schema pulls just once per endpoint
                 Key: CASSANDRA-13569
                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13569
             Project: Cassandra
          Issue Type: Bug
          Components: Distributed Metadata
            Reporter: Stefan Podkowinski
            Assignee: Stefan Podkowinski
             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
(v6.3.15#6346)

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


Mime
View raw message