We are currently performing testing with a two-code cluster of Azure A3 VMs with 7GB of memory per-node. We have the per-server ram quota set to the suggested amount of 4182MB. Everything works fine, except that rebalance operations seem to take a VERY long time, even with a small number of documents (roughly 250K docs @ 500MB total size).
One concern is that possibly the VMs are running short of memory during the rebalance. Looking at the “Memory Cache” section, it says that only 400MB are “In Use” but then 6.3GB is consumed by Other Data. Does that sound right, and is that something we should be concerned with?
I’m not sure how to gauge whether the cluster is experiencing memory pressure during the rebalance operation, but I want to make sure I understand what the “Other Data” mem calc means, and whether it’s something we need to be concerned about.
Any links to general memory management for Couchbase would be helpful as well, I did quite a bit of searching, and there isn’t much out there that describes how to determine if Couchbase is “healthy” from a memory perspective.