Some doubts on the use case

[arun11299]

Hello folks, I have few doubts on the use case of Dynomite. I have following scenario:

1. Two Redis instances are running in two different geographic locations. Running on Openstack Kubernetes cluster (two different clusters), if thats important.
2. I want them to be in ACTIVE-ACTIVE mode instead of MASTER-SLAVE because I want the instances to be writable on both locations.

Now I came across Dynomite few days back, it does what I need but only when both nodes are up and running. The data written at one location gets lost when:

1. In split brain scenarios.
2. When one of the node goes down for some reason.
3. There could be many other different scenarios leading to the above case.

Now, my question is:

1. Isn't this some feature that should have already been supported by Dynomite if I want to run them without Dynomite-manager ?
2. Is there any configuration to enable this ? Sorry, I did not find any in my search.
3. Is there anything else I can do so as to not miss any data. I could probably run some cron job in parallel to do the Redis dump and save. But that doesn't sound like a good solution especially when we are using something like Dynomite already. I would prefer if its solvable without using dynomite-manager. That will add more moving parts to our system.

Thanks in advance!!