ElasticSearch [5.4.1] 1 nous avons l'un indice comme ics_pcs_2017.06.06 2 nous supprimons l'une ancienne utilisation d'index code jave: getClient.admin ..() .indices() prepareDelete (nomindex) .Execute() actionGet()pas mis mappings sur indices écrasent la ElasticSearch [5.4.1]
I think the index ics_pcs_2017.06.06 will have 60G+ and 100,000,000 documents in it.
3 nous faisons un nouveau logstash pour recevoir les journaux anciens, et nous avons trouvé dans le journal ES: journaux ES info
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.
Souhaitez-vous certains wone aider et expliquer la raison, merci beaucoup.