You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ignite.apache.org by "Vladimir Ozerov (JIRA)" <ji...@apache.org> on 2017/03/02 11:58:45 UTC

[jira] [Created] (IGNITE-4769) Handle possibly duplicated discovery messages

Vladimir Ozerov created IGNITE-4769:
---------------------------------------

             Summary: Handle possibly duplicated discovery messages
                 Key: IGNITE-4769
                 URL: https://issues.apache.org/jira/browse/IGNITE-4769
             Project: Ignite
          Issue Type: Sub-task
          Components: SQL
            Reporter: Vladimir Ozerov
             Fix For: 2.0


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



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)