What are the configuration and read/write policy settings to achieve strong consistency in partitioned situations?
I understand that Aerospike makes all efforts to avoid partitions, but as discussed in this paper: http://www.aerospike.com/docs/architecture/assets/AerospikeACIDSupport.pdf, minority quorum can be halted. What is a configuration setting for that, does halt means that it will never re-join or just stops answering any requests?
Was there any progress implementing “static-cluster” method proposed in the paper?
Also, what is a Java client settings to enable strongly consistent reads? I can see C settings here : http://www.aerospike.com/docs/client/c/usage/consistency.html, but is there a Java alternative?
Ideally, there should be a situation where user request with reduced consistency could operate on minority quorum, and with strong consistency fail.
Thanks in advance Sasha