Hi,
What does it mean? GCP_SAVE lag .. seconds (no max lag)
How can I fix it?
What does it happen?
#cat ndb_1_cluster.log | grep WARNING
2015-03-09 04:31:12 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 60 seconds (no max lag)
2015-03-09 04:32:15 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 120 seconds (no max lag)
2015-03-09 04:33:17 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 180 seconds (no max lag)
2015-03-09 04:34:20 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 240 seconds (no max lag)
2015-03-09 04:35:23 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 300 seconds (no max lag)
2015-03-09 04:35:54 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_COMMIT lag 0 seconds (no max lag)
2015-03-09 04:36:26 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 360 seconds (no max lag)
2015-03-09 04:37:07 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_COMMIT lag 0 seconds (no max lag)
2015-03-09 04:37:28 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 420 seconds (no max lag)
2015-03-09 04:38:31 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 480 seconds (no max lag)
2015-03-09 04:39:34 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 540 seconds (no max lag)
2015-03-09 04:40:37 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 600 seconds (no max lag)
2015-03-09 04:41:40 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 660 seconds (no max lag)
2015-03-09 04:42:42 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 720 seconds (no max lag)
2015-03-09 04:43:45 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 780 seconds (no max lag)
2015-03-09 04:44:48 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 840 seconds (no max lag)
2015-03-09 04:45:51 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 900 seconds (no max lag)
2015-03-09 04:46:33 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_COMMIT lag 0 seconds (no max lag)
2015-03-09 04:46:54 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 960 seconds (no max lag)
2015-03-09 04:47:56 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 1020 seconds (no max lag)
2015-03-09 04:48:59 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 1080 seconds (no max lag)
2015-03-09 04:50:02 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 1140 seconds (no max lag)
What does it mean? GCP_SAVE lag .. seconds (no max lag)
How can I fix it?
What does it happen?
#cat ndb_1_cluster.log | grep WARNING
2015-03-09 04:31:12 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 60 seconds (no max lag)
2015-03-09 04:32:15 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 120 seconds (no max lag)
2015-03-09 04:33:17 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 180 seconds (no max lag)
2015-03-09 04:34:20 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 240 seconds (no max lag)
2015-03-09 04:35:23 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 300 seconds (no max lag)
2015-03-09 04:35:54 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_COMMIT lag 0 seconds (no max lag)
2015-03-09 04:36:26 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 360 seconds (no max lag)
2015-03-09 04:37:07 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_COMMIT lag 0 seconds (no max lag)
2015-03-09 04:37:28 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 420 seconds (no max lag)
2015-03-09 04:38:31 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 480 seconds (no max lag)
2015-03-09 04:39:34 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 540 seconds (no max lag)
2015-03-09 04:40:37 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 600 seconds (no max lag)
2015-03-09 04:41:40 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 660 seconds (no max lag)
2015-03-09 04:42:42 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 720 seconds (no max lag)
2015-03-09 04:43:45 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 780 seconds (no max lag)
2015-03-09 04:44:48 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 840 seconds (no max lag)
2015-03-09 04:45:51 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 900 seconds (no max lag)
2015-03-09 04:46:33 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_COMMIT lag 0 seconds (no max lag)
2015-03-09 04:46:54 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 960 seconds (no max lag)
2015-03-09 04:47:56 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 1020 seconds (no max lag)
2015-03-09 04:48:59 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 1080 seconds (no max lag)
2015-03-09 04:50:02 [MgmtSrvr] WARNING -- Node 3: GCP Monitor: GCP_SAVE lag 1140 seconds (no max lag)