Uploaded image for project: 'Cassandra'
  1. Cassandra
  2. CASSANDRA-13569

Schedule schema pulls just once per endpoint

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Open
    • Priority: Normal
    • Resolution: Unresolved
    • Fix Version/s: None
    • Labels:
      None

      Description

      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.

        Attachments

        1. 13569-trunk.patch
          3 kB
          Stefan Podkowinski

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                spod Stefan Podkowinski
                Reviewers:
                Aleksey Yeschenko
              • Votes:
                0 Vote for this issue
                Watchers:
                9 Start watching this issue

                Dates

                • Created:
                  Updated: