There exists a Mongo Replica Set with three nodes in three datacenters. A couple of all of them with data and also the other the first is an arbitrer

We're doing demanding creates however with almost 100% of securing therefore we do the reads within the replica node (secondary). Our problem would be that the reads are slow too within the secondary because of individuals creates.

Shall we be missing anything?

We're doing demanding creates however with almost 100% of securing therefore we do the reads within the replica node (secondary). Our problem would be that the reads are slow too within the secondary because of individuals creates.

Whenever you execute a email the main, that write also needs to be carried out around the secondary. Therefore the secondary does exactly the same act as the main.

If you have 100% securing around the primary, you've 100% securing around the secondary.

Moving reads towards the secondary most likely will not help since your IO around the primary is most likely completely locked therefore it can't continue.

Run iostat and top and determine in which the bottleneck is. The chances are you will need energy, however it might be an indexing problem.