From 8f2dde3bde7ee13259f213fe4741be7ef7f2d129 Mon Sep 17 00:00:00 2001
From: Ian Barwick <ian@2ndquadrant.com>
Date: Mon, 24 Jul 2017 12:50:51 +0900
Subject: [PATCH] repmgrd: log BDR node recovery on the running node, not the
 recovered node

The recovered node might still be starting up.
---
 repmgrd-bdr.c | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/repmgrd-bdr.c b/repmgrd-bdr.c
index ae3f32fe..361ad0e9 100644
--- a/repmgrd-bdr.c
+++ b/repmgrd-bdr.c
@@ -457,7 +457,8 @@ do_bdr_recovery(NodeInfoList *nodes, t_node_info *monitored_node)
 
 
 	// XXX check other node is attached to this one so we
-	// don't end up monitoring a parted node
+	// don't end up monitoring a parted node; if not attached,
+	// generate a failed bdr_recovery event
 
 
 	// note elapsed
@@ -475,7 +476,7 @@ do_bdr_recovery(NodeInfoList *nodes, t_node_info *monitored_node)
 		event_info.node_name = monitored_node->node_name;
 
 		create_event_notification_extended(
-			recovered_node_conn,
+			local_conn,
 			&config_file_options,
 			config_file_options.node_id,
 			"bdr_recovery",
@@ -486,7 +487,7 @@ do_bdr_recovery(NodeInfoList *nodes, t_node_info *monitored_node)
 	else
 	{
 		create_event_record(
-			recovered_node_conn,
+			local_conn,
 			&config_file_options,
 			config_file_options.node_id,
 			"bdr_recovery",