I’m new to Couchbase and am wondering are they any OS tweaks that should be done by default for a production cluster.
Coming from SQL for example, Postgresql needs a couple kernel setting tweaks like kernel.shmmax and kernal.shmmal
Those settings bump the shared memory for PGsql use as the default is quite low.
Anything similar for Couchbase?
I’ve just migrated an application to new servers which required an upgrade from Couchbase v1 to v3.
The previous sysadmin is not around, so I’m nutting it out by myself.
It’s up and running now but the 2 node Couchbase cluster is running with a load avg of:
load average: 5.24, 5.25, 5.23
This is higher than I’m used to so I’m wonder where to start looking (as a novice Couchbase administrator).
Does that load avg seem high to you as well?
I pretty much have all the settings at default.
Alerts are enabled and the test works but I haven’t received any Couchbase alerts as yet.
The two servers are quite beefy:
Base machine: E5-1620v2 2x500GB SATA, 16GB RAM
- 1 x E5-1620v2 CPU
- 16GB RAM (fastest available, please)
- 2 x 500GB SATA as 500GB software (mdadm) RAID1. Partitions:
- 100MB EXT4 boot partition, mount point ‘/boot’.
- 32GB swap partition.
- remaining capacity as EXT4 root (’/’) partition, Ubuntu 14.04.1 installed here.
I’m running version 3.0.0 Community Edition (build-1209) on Ubuntu 14.04.1.
One default couchbase bucket and four memcached buckets (only two in use currenlty).
The bucket details are:
- Couchbase Buckets (hit counter)
Bucket Name: default
Item Count: 177390
Disk Fetches/sec 0
RAM/Quota Usage: 121MB/4GB
Data/Disk Usage: 145MB/152MB
Access Control: None
Replicas: 1 replica copy
Compaction: Not active
Cache Metadata: Value Eviction
Disk I/O priority: Low
- Memcached Buckets (sql query cache)
Bucket Name: query-lt
Item Count: 427451
Hit Ratio: 86.4%
RAM/Quota Usage: 1.28GB /4GB
Bucket Name: query-xs
Item Count: 510876
Hit Ratio: 68.8%
RAM/Quota Usage: 1.68GB /4GB
Any tips, suggestions or advice is much appreciated.