-
Notifications
You must be signed in to change notification settings - Fork 1.4k
ElasticSearch 7+ "Native controller process has stopped - no new native processes can be started" #5029
Comments
adding |
@ediewoelfle Thank you. You save my day 👍 |
My environment is initially equipped with ES cluster, and one node always exits, and then reports Therefore, I switched to a single ES node and modified my My fix: Remove the previous volume binding directory directly(ES Cluster), and run docker again and everything is ok! My docker-compose.yml:
|
Looks like you are entered into production mode after explicit
It is required to do proper configuration setup since 7.0+ version. |
Thank you |
This helped me |
Expected behavior
Logs from a new 6.8.0 ES container:
Actual behavior
Logs from a new 7.2.0 ES container:
Information about the Issue
Every ES container above 6.8.0 fails to start.
Steps to reproduce the behavior
The text was updated successfully, but these errors were encountered: