I see about 20 mins of these log messages before it successfully starts up… until then elasticsearch is not reachable by logstash
I have a single node, 12GB jvm with about 1TB of data in about 400 indexes. With a 4GB JVM it used to take about 4 mins or of these error messages before it starts working.
Is there a systemic issue in my setup that is causing this issue at startup ?
[2021-02-11T15:51:26,177][ERROR][c.a.o.s.a.BackendRegistry] [wamapnap01] Not yet initialized (you may need to run securityadmin)
[2021-02-11T15:51:26,177][ERROR][c.a.o.s.a.BackendRegistry] [wamapnap01] Not yet initialized (you may need to run securityadmin)
[2021-02-11T15:51:26,661][INFO ][c.a.o.j.JobSchedulerPlugin] [wamapnap01] JobSweeper started listening to operations on index .opendistro-ism-config
[2021-02-11T15:51:26,871][ERROR][c.a.o.s.a.BackendRegistry] [wamapnap01] Not yet initialized (you may need to run securityadmin)
[2021-02-11T15:51:26,875][ERROR][c.a.o.s.a.BackendRegistry] [wamapnap01] Not yet initialized (you may need to run securityadmin)
[2021-02-11T15:51:26,986][INFO ][c.a.o.j.s.JobScheduler ] [wamapnap01] Scheduling job id -qcmmccbTiOTbdHGLKt4uQ for index .opendistro-ism-config .
[2021-02-11T15:51:26,988][INFO ][c.a.o.j.s.JobScheduler ] [wamapnap01] Scheduling job id 0WVfCBHzSXWDOmVydV1XHw for index .opendistro-ism-config .
[2021-02-11T15:51:26,988][INFO ][c.a.o.j.s.JobScheduler ] [wamapnap01] Scheduling job id 0xBhFD-NSVSclODPkrBdWg for index .opendistro-ism-config .