MembaseServer won't start unless other cluster instance is running
I installed MembaseServer on two machines (1.0.3). Both machines are running Win7 x64. On one machine, I installed the x64 MembaseServer (Instance A), and on the other I installed the x86 (Instance B). I joined Instance B to Instance A as a cluster.
When the machine with Instance A, I cannot start up Instance B. I get the error: "MembaseServer: Erlang machine stopped instantly (distribution name conflict?). The service is not restarted, ignoring OnFail option."
When I start up Instance A, I am then able to successfully start up Instance B.
I suspect this doesn't have anything to do with x64 vs x86, but that by joining Instance B to Instance A, it is somehow now dependent on Instance A being up before it can start. After joining the cluster, I would have expected these instances to start up successfully independently. If I'm in Production and Instance A is down for an extended period, I would hope that the cluster would still run with just Instance B.
I then removed Instance B from the cluster from the console on Instance A. I still can't start up Instance B independently. Maybe there's some kind of cluster configuration leftover that I have not been able to find.