Hi @regis, thanks for the reply, about your questions:
- the container was not stopped, when running
tutor local stop
, all containers were stopped and removed, but elasstic container was not stopped. - after some time the command
tutor local stop
finishes, but the elastic container was not stopped and I was not able to find an error log :(.
I’ve check the docker version installed, it was 17, and now is 19.03.6, with that upgrade now what is happening is that elastic container is always at 100% cpu (this was happening before too).
So maybe this inability of stopping the container was related with the version of docker that we are using.
@regis do you know if there is a way to re-index all the content and start again with elasticsearch data? I really can’t find the root cause of why elastic is always using 100% CPU.