The problem appears to be that resetCluster does not null cluster->master_names, resulting in a double free when proxy cluster update is called twice.
Calling clusterGetMasterNames was not strictly necessary but it seemed like the right thing to do to ensure the cluster struct is fully recreated by the update.
Fixes #66
The problem appears to be that
resetClusterdoes not nullcluster->master_names, resulting in a double free whenproxy cluster updateis called twice.Calling
clusterGetMasterNameswas not strictly necessary but it seemed like the right thing to do to ensure the cluster struct is fully recreated by the update.