From 66aa0d63fc205e27f7e2821d608cbcf4808eb21b Mon Sep 17 00:00:00 2001 From: Giles Westwood Date: Fri, 10 Jul 2015 11:11:55 +0100 Subject: [PATCH 1/2] Adding documentation regarding the importance of a single time source on conflict handlers --- doc/manual-conflicts.sgml | 7 ++++++- 1 file changed, 6 insertions(+), 1 deletion(-) diff --git a/doc/manual-conflicts.sgml b/doc/manual-conflicts.sgml index 16c808f238..0bdc1d8278 100644 --- a/doc/manual-conflicts.sgml +++ b/doc/manual-conflicts.sgml @@ -68,7 +68,12 @@ The most common conflicts are row conflicts where two operations affect a row with the same key in ways they could not do on a single node. &bdr; can detect most of those and apply last-update-wins conflict handling or invoke - a user-defined conflict handler. + a user-defined conflict handler. For the time based conflict handlers to + function correctly all nodes in the cluster must share the same time source. + If you have a conflict when the time on two nodes is out of sync the conflict + may never be able to resolved because the last update time will never match + even after the handler has run. This will manifest itself as row updates only + syncing in one direction. From b0c262fa61f327c03ee376549dc9cf8618680ce4 Mon Sep 17 00:00:00 2001 From: Giles Westwood Date: Wed, 15 Jul 2015 16:19:20 +0100 Subject: [PATCH 2/2] Adding link to node status docs as raised in issue #111 --- doc/manual-node-management.sgml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/doc/manual-node-management.sgml b/doc/manual-node-management.sgml index 83d1b39351..b19cb66086 100644 --- a/doc/manual-node-management.sgml +++ b/doc/manual-node-management.sgml @@ -104,6 +104,12 @@ See also: , . + + + To view the status of the cluster then interrogate this table:- . + + +