<html><head><style type="text/css"><!-- DIV {margin:0px;} --></style></head><body><div style="font-family:times new roman, new york, times, serif;font-size:12pt"><div style="font-family: times new roman,new york,times,serif; font-size: 12pt;">Sorry, another question!<br><br>In the Java client, I don't see the following scenario being taken care of:<br>0. Lets assume that we have one memcached server that is prone to failure. Lets call it bucket_1.<br>1. The remote cache is warmed before release, and we have some key/value pairs in bucket_1.<br>2. bucket_1 crashes, and on-demand our key_1 are remapped to bucket_2.<br> 2.A. The first get() would return a null, indicating a miss.<br> 2.B. We reload the data from the database and add it to bucket_2.<br>3. A user modifies some configuration data, and so we update our value for key_1 in bucket_2.<br>4. Some time later, we bring bucket_1 back online. It now has no data.<br>5. Our key_1 is requested,
hits bucket_1, and we get a miss/reload. Now, bucket_1 has the new data and bucket_2 has stale data.<br>6. bucket_1 crashes yet again.<br>7. key_1 is requested, is remapped to bucket_2, and now gets stale data.<br><br>This is obviously a small edge case and it would be difficult for the client to know that it needs to expire the value in bucket_2. More than likely the stale data is benign, but I believe the scenario is valid.<br><br>Thanks!<br>Ben<br></div></div><br>
<hr size=1><a href="http://us.rd.yahoo.com/evt=48226/*http://new.toolbar.yahoo.com/toolbar/features/norton/index.php">Get the free Yahoo! toolbar</a> and rest assured with the added security of spyware protection.
</body></html>