Understanding Timeout and Retry policies

[kporter]

I previously described a solution here:

Handling timeout in case of counter bin

To rephrase the question, “is there a way to know if a write definitely applied or definitely didn’t apply?” First, timeouts are not the only error you should be concerned with. Newer clients have an ‘inDoubt’ flag associated with errors that will indicate that the write may or may not have applied. There isn’t a built-in way of resolving an in-doubt transaction to a definitive answer and if the network is partitioned, there isn’t a way in AP to rigorously resolve in-doubt transactions. Rigo…

Note that this solution is specific to a counter, if you need read/modify/write then change step 2 (getHeader) to retrieve the full record.