Uploaded image for project: 'Ignite'
  1. Ignite
  2. IGNITE-4565 Support CREATE INDEX DDL statements
  3. IGNITE-4769

Handle possibly duplicated discovery messages

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • 2.0
    • sql
    • None

    Description

      Problem
      It is known that discovery message notifications could be invoked more than once in case of unsuccessful concurrent topology changes. We need to protect DDL logic from it somehow.

      Proposed solution
      1) Add bounded set holding unique operation IDs.
      2) Ignore init/ack message when ID already exists in history set.
      3) Control maximum history size through system property.

      Attachments

        Activity

          People

            vozerov Vladimir Ozerov
            vozerov Vladimir Ozerov
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: