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.