Maybe next week we can all explore this.
I'm on 3.10.5 and I don't have any complaints. Actually we are quite
happy with the new clusters, but these were green field installations
that were built and then replaced our old 3.4 stuff.
So we are still really enjoying the sharding and arbiter
On 22/09/2017 1:21 PM, Krutika Dhananjay wrote:
Could you disable cluster.eager-lock and try again?
Thanks, but didn't seem to make any difference.
Can't test anymore at the moment as down a server that hung on reboot :(
--
Lindsay Mathieson
Could you disable cluster.eager-lock and try again?
-Krutika
On Thu, Sep 21, 2017 at 6:31 PM, Lindsay Mathieson <
lindsay.mathie...@gmail.com> wrote:
> Upgraded recently from 3.8.15 to 3.10.5 and have seen a fairly substantial
> drop in read/write perfomance
>
> env:
>
> - 3 node, replica 3
Upgraded recently from 3.8.15 to 3.10.5 and have seen a fairly
substantial drop in read/write perfomance
env:
- 3 node, replica 3 cluster
- Private dedicated Network: 1Gx3, bond: balance-alb
- was able to down the volume for the upgrade and reboot each node
- Usage: VM Hosting (qemu)
-
