Loading...

XML

Word

Printable

Using the MERGE3 protocol, it can take significantly longer than max_interval for merge to happen.

The info sender interval is up to 45 seconds

        public long nextInterval() {
            return Math.max(min_interval, Util.random(max_interval) + max_interval/2);
        }

and the view consistency checker interval is 48 seconds

    protected long computeCheckInterval() {
        return (long)(max_interval * 1.6);
    }

which depending on the timing seem to take significant amount of time.

is blocked by

JGRP-2281 MERGE3 blocks unnecessarily in discovery when non-multicast transport is used

relates to

WFLY-9771 SingletonPartitionTestCase.testSingletonService fails intermittently