Closed steve-butler closed 4 years ago
Thank you, Steve! The manual work-around is what we had in mind. We were not aware of the stats_collector info on the VSD. We will create a JIRA ticket and implement an enhancement as you have suggested.
METROAE-1061
Resolved in v4.0
src/roles/vsd-cluster-failover/tasks/main.yml hard codes the active elasticsearch cluster as hostvars[groups['vstats'][0]]['hostname'],hostvars[groups['vstats'][1]]['hostname'],hostvars[groups['vstats'][2]]['hostname'] If vsd-cluster-failover runs while standby ES is active, stats could get lost by ES backup/restore.
Manual workaround: Change the order of servers in vstats deployment file.
Partial Code Solution: Get active elasticsearch hosts list from primary VSD config file. Use output in vsd-switch-replication-cluster-role command. Something like this:
This solution only work if primary cluster is reachable.