[jboss-jira] [JBoss JIRA] (WFLY-9420) Partitions can take up to 2 minutes to merge
[
https://issues.jboss.org/browse/WFLY-9420?page=com.atlassian.jira.plugin....
]
Radoslav Husar updated WFLY-9420:
---------------------------------
Description:
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
{code}
public long nextInterval() {
return Math.max(min_interval, Util.random(max_interval) + max_interval/2);
}
{code}
and the view consistency checker interval is 48 seconds
{code}
protected long computeCheckInterval() {
return (long)(max_interval * 1.6);
}
{code}
which depending on the timing can take significant amount of time.
was:
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
{noformat}
public long nextInterval() {
return Math.max(min_interval, Util.random(max_interval) + max_interval/2);
}
{noformat}
and the view consistency checker interval is 48 seconds
{noformat}
protected long computeCheckInterval() {
return (long)(max_interval * 1.6);
}
{noformat}
Partitions can take up to 2 minutes to merge
--------------------------------------------
Key: WFLY-9420
URL: https://issues.jboss.org/browse/WFLY-9420
Project: WildFly
Issue Type: Bug
Components: Clustering
Affects Versions: 11.0.0.CR1
Reporter: Radoslav Husar
Assignee: Radoslav Husar
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
{code}
public long nextInterval() {
return Math.max(min_interval, Util.random(max_interval) + max_interval/2);
}
{code}
and the view consistency checker interval is 48 seconds
{code}
protected long computeCheckInterval() {
return (long)(max_interval * 1.6);
}
{code}
which depending on the timing can take significant amount of time.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)