Logging stack fails with "java.lang.IllegalArgumentException: Unknown Discovery type"
Issue
- ES containers do not come up (in crash loop) with the following output:
[2017-09-21 19:09:40,650][INFO ][container.run ] Begin Elasticsearch startup script
--
| [2017-09-21 19:09:40,663][INFO ][container.run ] Comparing the specified RAM to the maximum recommended for Elasticsearch...
| [2017-09-21 19:09:40,664][INFO ][container.run ] Inspecting the maximum RAM available...
| [2017-09-21 19:09:40,668][INFO ][container.run ] ES_HEAP_SIZE: '1024m'
| [2017-09-21 19:09:40,669][INFO ][container.run ] Setting heap dump location /elasticsearch/persistent/heapdump.hprof
| [2017-09-21 19:09:40,672][INFO ][container.run ] Checking if Elasticsearch is ready on https://localhost:9200
| Exception in thread "main" java.lang.IllegalArgumentException: Unknown Discovery type [kubernetes]
| at org.elasticsearch.discovery.DiscoveryModule.configure(DiscoveryModule.java:100)
| at <<<guice>>>
| at org.elasticsearch.node.Node.<init>(Node.java:213)
| at org.elasticsearch.node.Node.<init>(Node.java:140)
| at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:143)
| at org.elasticsearch.bootstrap.Bootstrap.setup(Bootstrap.java:194)
| at org.elasticsearch.bootstrap.Bootstrap.init(Bootstrap.java:286)
| at org.elasticsearch.bootstrap.Elasticsearch.main(Elasticsearch.java:45)
| Refer to the log for complete error details.
Environment
- Openshift Container Platform
- 3.6
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.
Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.
