High CPU on master and client nodes only when indexing

I'm trying to track down a problem when CPU load on dedicated coordinating and master nodes closely follows indexing activity under some unclear yet circumstances. From what I know about these two types, they should not experience any significant load when indexing is happening, unless maybe when data mappings change significantly with a large number of different fields coming in with every document. That's not the case however and I don't see this all the time. Any idea what specific type of activity can cause such synchronous jumps?

Screen_Shot_2018-03-07_at_3_48_27_PM

Thanks.

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.