First of all thanks for your quick replies.
There is no XDCR but there is 1 view document with 9 views and 1 index for N1QL. But none of the views is particularly complex - they are more like secondary indexes which do emit just hand full of fields.
Even though I’m aware that at least 4 cores are recommended these machines are only dual-core but that shouldn’t be any issue if there is very little load on the system, right?
The machines do have 30 GB of ram whereby 14336 MB are allocated for data and 2048 MB for index. So there should be enough spare RAM for the other processes.
@daschl the cluster is rather simple:
A simple 2 node cluster in the OVH Public Cloud with SP-30 instances (I know 3 nodes are recommended but for testing I decided to use 2 nodes)
Both servers are synchronizing their system time with an NTP server.
I’m using a private network (OVH vRack with the 10.0.0.0/24 IP range)
There is no packet loss on the network connection - the ping is stable and between 0.5 and 2.5 ms
Servers are configured using host names - DNS resolution time shouldn’t be an issue either because I’ve added all host names and IP addresses to the /etc/hosts file
The application accessing Couchbase is situated in the same vRack (so no big delays their either)
Both servers are running all services (Data, Index, Query) and yes, I’m also using N1QL
In case you have any additional questions I’m happy to answer them
If needed I can also provide log files