"TTLs" means expiration time of objects, doesn't it? If Memcached servers are down and up in a short period of time ( for example: the LAN cable flicker again and again ...) I could not use the 1st option. I think the 2nd option is safe enough.
Thank you. On Wed, Sep 28, 2011 at 7:51 PM, Brian Moon <[email protected]> wrote: > Two options: > > 1. Use short TTLs and don't worry about it. > 2. Don't use failover and when S2 is down, all requests will be misses. > > Brian. > http://brian.moonspot.net > > > On 9/28/11 6:28 AM, thibd wrote: > >> Dear all, >> >> I am a newbie to Memcached >> I am now feeling difficulte to ensure my app not to get out of date >> data due to this scenario: >> - having one server S1 (with key k1-value1, k2-value2) >> - adding one more server S2, and then "value1" is stored in S1, and >> "value2" is stored in both S1 and S2 (the app just retrives value for >> k2 from S2). >> - "value2" in S2 is updated, and "value2" in S1 will be out of date. >> - S2 down suddenly and then the app will try to get value of key k2 >> from S1, it means the out of date data will be used. >> >> I've tried to find out solution from internet but there is not enough >> info. would you please give me some instruction to solve the issue? >> >> Thank all. >> >> >> >>
