The new cluster is a mirror image of the old cluster resources wise - same number of virtual CPUs, RAM, etc. The major differences is we updated to Windows Server 2016, and updated to the latest version of Couchbase.
As for enabled services in CouchBase 5.5, we’re only running the data service since we’re only doing the most basic document gets/sets against it.
Configuration:
<couchbase operationTracingEnabled=“false” operationTracingServerDurationEnabled=“false”
enableOperationTiming=“false” enableQueryTiming=“false” xdt:Transform=“Replace”>
<servers>
<add uri=“http://…-1…:8091” />
<add uri=“http://…-2…:8091” />
<add uri=“http://…-3…:8091” />
<add uri=“http://…-4…:8091” />
<add uri=“http://…-5…:8091” />
<add uri=“http://…-6…:8091” />
</servers>
<buckets>
<add name=“bucketName” operationLifespan=“120000”>
<connectionPool name=“custom” maxSize=“100” minSize=“10” connectTimeout=“20000” sendTimeout=“120000” />
</add>
</buckets>
</couchbase>
Note:
The trace/timing were disabled to deal with the issue mentioned here:
operationTracingEnabled=“false”
operationTracingServerDurationEnabled=“false”
enableOperationTiming=“false”
enableQueryTiming=“false”
I’ll try MeepMeep today, and post the results.