2 ms·
I'm not sure what you've added here other than to exclaim surprise. Bugs can be surprising, bugs are usually not intentional. Given the fast response by the etc
by leorocky 12y ago
I'm not sure what you've added here other than to exclaim surprise. Bugs can be surprising, bugs are usually not intentional. Given the fast response by the etcd team, they seem to be taking consistency very seriously.
- aaronblohowiak 12y agoThis was not a bug, it was a design decision (source: https://github.com/coreos/etcd/issues/741 https://github.com/coreos/etcd/issues/741 ) . You can get stale data in some circumstances because they wanted to avoid the performance penalty of ensuring the latest really is the latest value from a quorum of followers.
- teraflop 12y agoThere's the design decision, and then there's the incorrect documentation that says reads with "consistent=true" are guaranteed to return the latest value. https://github.com/coreos/etcd/blob/master/Documentation/api.md#read-consistency https://github.com/coreos/etcd/blob/master/Documentation/api...