Closed pavolloffay closed 6 years ago
@pavolloffay This looks good, but in my initial attempt to get it to run on my own minishift instance I got this error in the ElasticSearch pod:
| [1]: max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144]
Can you tell me what I need to do to get past this?
Update: I just looked at the CNCF CI, and there ES gets the same message but doesn't consider it an error:
| [2018-03-15T16:47:19,899][WARN ][o.e.b.BootstrapChecks ] [master] max virtual memory areas vm.max_map_count [65530] is too low, increase to at least [262144] | [2018-03-15T16:47:24,914][WARN ][o.e.d.z.UnicastZenPing ] [master] timed out after [5s] resolving host [elasticsearch-discovery] | [2018-03-15T16:47:27,927][INFO ][o.e.c.s.ClusterService ] [master] new_master {master}{mksoUnPCRESRVWmznOAa3g}{5jv8rY_wQRmj_1mY-Z1Dfw}{127.0.0.1}{127.0.0.1:9300}, reason: zen-disco-elected-as-master ([0] nodes joined) | [2018-03-15T16:47:27,937][INFO ][o.e.h.n.Netty4HttpServerTransport] [master] publish_address {172.17.0.9:9200}, bound_addresses {[::]:9200} | [2018-03-15T16:47:27,937][INFO ][o.e.n.Node ] [master] started | [2018-03-15T16:47:27,944][INFO ][o.e.g.GatewayService ] [master] recovered [0] indices into cluster_state
@pavolloffay Now this is failing on the CNCF CI because it considers "max virtual memory areas vm.max_map_count [65530] is too low" to be an error instead of just ignoring it.
Elastic requires this limit, @kevinearls could you please fix it as soon as possible?
Wohoo I got Jenkins to pass. I will merge as it is approved. If there are any more comments I will handle them in a separate PR
Also I have changed limits on the node so it works.
@pavolloffay think it would be better to get @kevinearls to review this one.