.Opendistro_Security Index Does Not Persist Container Restarts

After we initialize the index, if we restart our containers, the index is no longer initialized. Is this expected behavior? Shouldn’t it be stored persistently like any other index so that it survives new container deployments?

Mike

Just a comment here that even if the message is seen, it does not make me run securityadmin.sh again. I had run just once.

Having the exact same problem, anyone found a solution?

[2020-07-02T15:27:47,667][INFO ][c.a.o.s.OpenDistroSecurityPlugin] [elasticsearch-master-0] Node started

7/2/2020 5:27:47 PM [2020-07-02T15:27:47,667][INFO ][c.a.o.s.c.ConfigurationRepository] [elasticsearch-master-0] Check if .opendistro_security index exists ...

7/2/2020 5:27:47 PM [2020-07-02T15:27:47,667][INFO ][c.a.o.s.c.ConfigurationRepository] [elasticsearch-master-0] .opendistro_security index does not exist yet, so we create a default config

Hi All, The containers need to be mapped to a persistent volume to save the security index together with other data, if during restart of containers the volume is wiped clean then the security index is re-created again. How are you running the containers? Is it using helm? Also which odfe version are you using?