Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
2.3.2
-
None
Description
The cluster synchronization on a slave does always wait for some time (as specified in the sync delay) before fetching changes. If a lot of changes are being written to the master, a slave will considerably fall behind the master in term of revisions, which may endanger the integrity of the cluster if the master will crash. I therefore suggest that a slave should rather immediately contact the master again after some changes have been found, until it sees no more changes.
Attachments
Issue Links
- breaks
-
JCR-3427 JCR-3138 may cause resource starvation
- Closed