-
Bug
-
Resolution: Done
-
Major
-
3.6.3
-
None
When using TUNNEL transport with MERGE2 discovery protocol, cluster merge doesn't happen.
Problem seems to be in MERGE2.FindSubgroupsTask.fetchViews() method, which returns immediately after sending multicast discovery request instead of waiting for reply(ies). This is in contradiction with its' contract: "Returns when either discovery_timeout ms have elapsed or more than 1 different view has been found".
Different views are therefore not detected and MERGE event is not generated.
Everything works fine when using MERGE3 discovery protocol instead.