It is expected behavior to a degree.
It is true that every node is like every other node, but there are
actually some internal, non-critical processes that run in one and only
one place. This probably accounts for the additional CPU utilization.
The other thing that may account for it is that all of your moxis may be
pointed to that one system. It is actually a best practice to distribute
the moxi load and there is (unfortunately) a known bug with memory
utilization from client connections that should be addressed soon. We've
only seen it actually affect things in very large deployments.
Hope that helps,
Matt
--
Matt Ingenthron
Couchbase, Inc.
--chad
Thanks for the feedback. I checked out the problem node and see in top
that the %CPU fluctuates wildly between lowish values (~30%) and high
values (108%?). However the load average is quite low. On the other
(non-problematic) nodes however, the %CPU is only sitting around 2 -
5% which corresponds with what I see on the admin page.
As for the moxi clients being pointed to the one system, I have the
moxi-cluster config set up for each bucket with the pipe-separated
string of all 3 server nodes. However all cluster config files on all
machines have exactly the same server order (the problem server is
last). I'm not sure if the order is a factor.
Actually, it appears to be alternating between memcached and beam.smp.
They really are both fluctuating fairly rapidly across a wide range of
values.