EFK环境下的es集群告警信息

这个是master，elasticsearch-logging-0那就应该是slave了。
[2019-11-25T02:29:05,971][WARN ][o.e.m.j.JvmGcMonitorService] [elasticsearch-logging-1] [gc][3601] overhead, spent [2.1s] collecting in the last [2.1s]
[2019-11-25T02:29:16,927][WARN ][o.e.m.j.JvmGcMonitorService] [elasticsearch-logging-1] [gc][3611] overhead, spent [1.8s] collecting in the last [1.8s]
[2019-11-25T02:29:20,811][WARN ][o.e.m.j.JvmGcMonitorService] [elasticsearch-logging-1] [gc][3614] overhead, spent [1.8s] collecting in the last [1.8s]
[2019-11-25T02:29:29,889][WARN ][o.e.m.j.JvmGcMonitorService] [elasticsearch-logging-1] [gc][3621] overhead, spent [2.2s] collecting in the last [3s]
[2019-11-25T02:29:29,939][WARN ][o.e.d.z.PublishClusterStateAction] [elasticsearch-logging-1] timed out waiting for all nodes to process published state [4758] (timeout [30s], pending nodes: [{elasticsearch-logging-0}{DRHAQw4VSlKy06CHxaDmqw}{m0a-_88bRP-VUulBe5if4g}{172.30.56.6}{172.30.56.6:9300}])
[2019-11-25T02:29:29,985][WARN ][o.e.c.s.MasterService ] [elasticsearch-logging-1] cluster state update task [shard-started StartedShardEntry{shardId [[logstash-2019.07.13][4]], allocationId [Ql-mVTvYQjqSe0dvHClmmQ], message [after peer recovery]}[StartedShardEntry{shardId [[logstash-2019.07.13][4]], allocationId [Ql-mVTvYQjqSe0dvHClmmQ], message [after peer recovery]}], shard-started StartedShardEntry{shardId [[logstash-2019.07.13][4]], allocationId [Ql-mVTvYQjqSe0dvHClmmQ], message [master {elasticsearch-logging-1}{11EauWJsSgG1ZtgnGsC6TA}{nCHWtuEhQ0OgkbHZWz48Kw}{172.30.136.8}{172.30.136.8:9300} marked shard as initializing, but shard state is [POST_RECOVERY], mark shard as started]}[StartedShardEntry{shardId [[logstash-2019.07.13][4]], allocationId [Ql-mVTvYQjqSe0dvHClmmQ], message [master {elasticsearch-logging-1}{11EauWJsSgG1ZtgnGsC6TA}{nCHWtuEhQ0OgkbHZWz48Kw}{172.30.136.8}{172.30.136.8:9300} marked shard as initializing, but shard state is [POST_RECOVERY], mark shard as started]}]] took [32.3s] above the warn threshold of 30s