Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Elasticsearch virtual memory error #167

Open
RichardScottOZ opened this issue Aug 12, 2022 · 4 comments
Open

Elasticsearch virtual memory error #167

RichardScottOZ opened this issue Aug 12, 2022 · 4 comments

Comments

@RichardScottOZ
Copy link
Contributor

es01                | {"type": "server", "timestamp": "2022-08-12T08:17:23,741Z", "level": "INFO", "component": "o.e.t.TransportService", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "publish_address {10.0.1.9:9300}, bound_addresses {0.0.0.0:9300}" }
es01                | {"type": "server", "timestamp": "2022-08-12T08:17:23,892Z", "level": "INFO", "component": "o.e.b.BootstrapChecks", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "bound or publishing to a non-loopback address, enforcing bootstrap checks" }
es01                | ERROR: [1] bootstrap checks failed
es01                | [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
es01                | ERROR: Elasticsearch did not exit normally - check the logs at /usr/share/elasticsearch/logs/es-docker-cluster.log
es01                | {"type": "server", "timestamp": "2022-08-12T08:17:23,899Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "stopping ..." }
es01                | {"type": "server", "timestamp": "2022-08-12T08:17:23,910Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "stopped" }
es01                | {"type": "server", "timestamp": "2022-08-12T08:17:23,910Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "closing ..." }
es01                | {"type": "server", "timestamp": "2022-08-12T08:17:23,921Z", "level": "INFO", "component": "o.e.n.Node", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "closed" }
es01                | {"type": "server", "timestamp": "2022-08-12T08:17:23,922Z", "level": "INFO", "component": "o.e.x.m.p.NativeController", "cluster.name": "es-docker-cluster", "node.name": "es01", "message": "Native controller process has stopped - no new native processes can be started" }

Is that suggesting server should have 256GB minimum to run this?

@RichardScottOZ
Copy link
Contributor Author

Which would seem like something to run on a non-GPU machine - e.g. 'the already have server' section?

@RichardScottOZ
Copy link
Contributor Author

Leading back to the quick advice on setup section.

@iross
Copy link
Contributor

iross commented Aug 15, 2022

Is that suggesting server should have 256GB minimum to run this?

Nope, it can run on much much less -- if I remember correctly, these are just counts of memory maps available to the Elasticsearch JVM, as opposed to MB. It's a system setting, and I'll have to look at the ES documentation to see if there's a way for the ES instance to accept the lower system setting (accepting any potential performance or stability hits).

@RichardScottOZ
Copy link
Contributor Author

Thanks - I was just running it on a 32GB RAM gpu as a cheap test - ironically gpu bit didn't work. :)

Instant search engine capability is certainly appealing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants