ElasticSearch는 [5.4.1] (1) 우리는 우리가 일부 이전 인덱스를 사용 jave 코드를 삭제 ics_pcs_2017.06.06 2와 같은 일부 인덱스가 인덱스에 매핑이 elasticsearch 충돌 넣어 실패 ..() .indices() prepareDelete (INDEXNAME) .Execute를() actionGet는()은 [5.4.1]
I think the index ics_pcs_2017.06.06 will have 60G+ and 100,000,000 documents in it.
3 우리는 새로운 logstash 오래된 로그를받을 수 있도록, 우리는 ES 로그에 : ES 로그 정보
을create index for ics_pcs_2017.06.06(didn't get the detail log)
.....
[o.e.c.m.MetaDataCreateIndexservice] create index cause [auto(bulk api)], templates[icstemplate],shards [6]/[1], mappings [icslog]
.....
[o.e.c.m.MetaDataCreateIndexservice] [ics_pcs_2017.06.06/xtNoHLSOS4GBQo01-Nprg] update_mapping [icslog]
...
[o.e.a.a.1.m.p.TransportPutMappingAction] [ics-master1] failed to put mappings on indices[[[ics_pcs_2017.06.06/xtNoHLSOS4GBQo01-Nprg]]]
org.elasticsearch.cluster.metada.ProcessClusterEventTimeoutException:failed to process cluster event(put-mapping) within 30s
....
-----------
then there is many logs like failed to put mappings on indices[[[ics_pcs_2017.06.06/xtNoHLSOS4GBQo01-Nprg]]]
... failed to put mappings on indices[[[ics_pcs_2017.06.06/xtNoHLSOS4GBQo01-Nprg]]]
...failed to put mappings on indices[[[ics_pcs_2017.06.06/xtNoHLSOS4GBQo01-Nprg]]]
and cause the elasticsearch master down.
몇몇은 도움을주고 이유를 설명하고, 고맙게 여긴다.