This content has been marked as final. Show 3 replies
It sounds as if you're talking about the DB_TXN_NOSYNC flag, rather than DB_NOSYNC.
You mention that in general, you lose uncommitted transactions on system failure. I think what you mean is that you may lose some committed transactions on system failure. This is correct.
It is also correct that if you use replication you can arrange to have clients have a copy of all committed transactions, so that if the master fails (and enough clients do not fail, of course) then the clients still have the transaction data, even when using DB_TXN_NOSYNC.
This is a very common usage scenario for Berkeley DB replication/HA, used to achieve high throughput. You will want to pay attention to the configured ack policy, group size setting, setting of the 2SITE_STRICT option (if group size == 2).
Yes i am talking about DB_TXN_NOSYNC flag.
You also have right about losing commited transactions.
My group size is larger than 2 so i don't need 2SITE_STRICT.
If you can provide me with some information about configuring ack policy, like a documentation or something, would be very helpful.