Log file Viewer

[11:37:11] <pagios> hello, how can i check if mongo db is being stressed and slowly at responding?

[15:25:53] <blackleitus> why line 13 and 17 goes 50s+ ? https://dpaste.org/TcD6#L13,17

[15:40:10] <jindraj> I'm observing increased load average on primary server in replicaset after upgrading from 4.2.x to 4.4.1 (tried 4.4.2 today). I tried downgrading and sofar it seems it's back to normal. Any Idea what could be causing this? The workload is the same.

[16:21:11] <jindraj> I can see in grafana dashboard that after upgrade to 4.4.x it started to do a lot of getmores - approx 4x-4.5x more. downgrade to 4.2.x drops it back to normal.

[16:24:47] <d4rkp1r4t3> are the nodes you are upgrading to 4.4.x down for a long period of time? I wonder if the increase in getmores are secondaries trying to catch back up to the primary. doesn't explain why downgrading to 4.2.x decreases the frequency though..

[16:27:51] <jindraj> d4rkp1r4t3: nope. it's nearly atomic. I was running 4.4.x for about a week. the workload is the same. I didn't notice any difference between 4.4.1 and 4.4.2, but downgrade did the thing.

[16:29:32] <jindraj> I'll try to look into JIRA if there's any similar issue. If not I'll try to find what's needed for issue report.

[16:30:44] <d4rkp1r4t3> probably related to this: https://docs.mongodb.com/manual/release-notes/4.4/#streaming-replication

[16:31:30] <d4rkp1r4t3> you can go back to the 4.2.x behavior with replication by using the oplogFetcherUsesExhaust startup parameter though.

[16:33:41] <jindraj> d4rkp1r4t3: might be. Thanks. I'll try tomorrow and report you back if it helped.

[17:34:04] <d4rkp1r4t3> no prob. looking forward to hearing back the results