Yup :) looks like you left a system installed version of memcached running
on the other one.
On Mon, 16 Dec 2019, Alireza Sanaee wrote:
> Hi,
> I did a stupid mistake, the big machine Memcached version seems different. I
> guess that is the problem.
>
> Thanks,
> Alireza
>
> On Mon, Dec 16,
Hi,
I did a stupid mistake, the big machine Memcached version seems different.
I guess that is the problem.
Thanks,
Alireza
On Mon, Dec 16, 2019 at 2:16 AM Alireza Sanaee wrote:
> Hi,
>
> I'm investigating the Linux load balancer, meanwhile, I'm trying to
> understand what is happening in
Hi,
I'm investigating the Linux load balancer, meanwhile, I'm trying to
understand what is happening in Memcached and just noticed the different
number of Memcached threads on my machines. Linux doesn't provide
immediate access to generally latency-sensitive threads/processes like
Memcached
What're you trying to accomplish?
Can you include the output of "stats" and "stats settings" on both
machines?
Dumb question but you've looked at the output of `ps auxH`? If just using
htop you may not see the threads that're idle.
TCP connections are pinned to a specific worker thread on
What version of memcached is on each machine?
memcached doesn't use processes, it's multi-threaded. Different versions
may have a different number of background threads. In the latest version
there should be at least:
- listener thread (main "process")
- N worker threads
- hash table maintenance
Hello,
I'm running Memcached on two different machines with different
specifications. And I specify the number of worker threads = 4 for both
machines. However, the number of child processes of the Memcached server is
different on two machines. On one of them, I have 6 Memcached child
