Seeing frequent "goxdcr on node 'babysitter_of_ns_1@127.0.0.1' exited with status 1" during database path change

Port server goxdcr on node 'babysitter_of_ns_1@127.0.0.1' exited with status 1. Restarting. Messages: MetadataService 2015-06-01T13:06:36.949-07:00 [ERROR] metakv.ListAllChildren failed. path=/remoteCluster/, err=Post http://127.0.0.1:8091/_metakv: CBAuth database is stale: last reason: dial tcp 127.0.0.1:8091: connection refused, num_of_retry=2
MetadataService 2015-06-01T13:06:36.949-07:00 [ERROR] metakv.ListAllChildren failed. path=/remoteCluster/, err=Post http://127.0.0.1:8091/_metakv: CBAuth database is stale: last reason: dial tcp 127.0.0.1:8091: connection refused, num_of_retry=3
MetadataService 2015-06-01T13:06:36.949-07:00 [ERROR] metakv.ListAllChildren failed. path=/remoteCluster/, err=Post http://127.0.0.1:8091/_metakv: CBAuth database is stale: last reason: dial tcp 127.0.0.1:8091: connection refused, num_of_retry=4

RemoteClusterService 2015-06-01T13:06:36.949-07:00 [ERROR] Failed to get all entries, err=metakv failed for max number of retries = 5
[goport] 2015/06/01 13:06:36 /opt/couchbase/bin/goxdcr terminated: exit status 1

Is this something expected ? I see this typically during topology changes on the cluster, eg: rebalance in , rebalance out etc.

Adding logs.