Comment #5 on issue 151 by [email protected]: Append/Prepend to existing key whose value that grows larger than 1MB and non-existing key returns NOT_STORED error
http://code.google.com/p/memcached/issues/detail?id=151
Looks like you have the one edge case that's annoyed by this. Thanks for explaining it.
If you need to use a workaround, I'd still suggest something like add. You throw away an RTT still but don't fetch a lot of data back.
Then you're somewhat stuck with appending to keys you don't want to append to... You could mitigate it a bit by having the "add" add a key with a timeout of 1s, making it less likely that it'll fill to the brim with data.
Your case does seem a little weird though. If it's failing to append due to hitting the item size limit, you just leave it at 1M? You don't trim it or want to rewrite it? In most apps I run a failure due to overlarge value or nonexistent key are both good reasons to re-add a compacted item.
This kinda makes me want to add a new command... something like "-X" which enables protocol fixes, with the caveat that we can add protocol fixes in every release. A method to bridge the gap between major releases, perhaps?
