You can't evict memory that's being used to load data from the network.
So if you have a low amount of memory and run a benchmark doing a bunch of
parallel writes you're going to be sad.
On Tue, 1 Jun 2021, Qingchen Dang wrote:
> Thank you very much! Yes your guess is correct, I forgot the
Thank you very much! Yes your guess is correct, I forgot the possibility of
evicting a crawler item :(
Furthermore, I have a similar problem as this
post: https://github.com/memcached/memcached/issues/467
I gave a very limited memory usage to Memcached to test eviction and it
does cause the
try '-o no_lru_crawler' ? That definitely works.
I don't know what you're doing since no code has been provided. The locks
around managing LRU tails is pretty strict; so make sure you are actually
using them correctly.
The LRU crawler works by injecting a fake item into the LRU, then using
that
Furthermore, I tried to disable the crawler with the '- no_lru_crawler'
command parameter, and it gives the same error. I wonder why it does not
disable the crawler lru as it supposes to do.
On Monday, May 31, 2021 at 1:02:38 AM UTC-4 Qingchen Dang wrote:
> Hi,
>
> I am implementing a
Hi,
I am implementing a framework based on Memcached. There's a problem that
confused me a lot. The framework basically change the eviction policy, so
when it calls to evict an item, it might not evict the tail item at COLD
LRU, instead it will look for a "more suitable" item to evict and it
