If the dedicated master node are experiencing high CPU this often means that it is busy updating the cluster state and propagating these changes across the cluster. This can be caused by having a lot of shards (this seems to be the case here) or frequently updating mappings.
I would also recommend checking in the logs whether the master node is suffering from long or frequent GC.