-
Notifications
You must be signed in to change notification settings - Fork 4
Open
Description
Discovered when trying to set up both realtime and fullsync NextGenRepl between 2 fully functional clusters of identical node count where all nodes were running KV 3.2.4. As part of setting up fullsync, the ttaaefs_peerip setting in the source cluster has to point to the fullsync peer in the sink cluster. As an FQDN had been set up for each node, we put the FQDN in instead of the IP address in the ttaaefs_peerip setting on the source cluster. This caused Riak to fall over silently with no log of cause. This was remedied by changing it to a hard-coded IPv4 address.
When using an environment where IP addresses can change, this seems to contradict Riak's ability to use an FQDN in the nodename.
To replicate:
- Create two clusters
- Set up NextGenRepl as one would normally
- On a source node, set
ttaaefs_peeripto an FQDN that points to a sink node - Restart Riak on the source node you updated
- Check whether Riak started.
- On the same source node, change
ttaaefs_peeripto the IPv4 address of the same sink node. - Restart Riak on the source node you updated.
- Check whether Riak started.
Metadata
Metadata
Assignees
Labels
No labels