ES cluster cannot startup #9
Comments
@jimmidyson would it be possible to just get the service endpoints instead of retrieving all pods? After all, we're just looking for IP addresses. Something like: final Endpoints endpoints = getKubernetes().endpointsForService(this.selector, null);
for (String endpoint : endpoints.getEndpoints()) {
// instantiate DiscoveryNode
} I can provide a PR but would like to know if we agree on this. |
@mulloymorrow - raised fabric8io/kubernetes-model#25 to sort this out. Will try to get a new release out asap. Thanks for the report. @pires - sounds good to be, much more efficient. |
@mulloymorrow would you be able to share the manifest causing the issue so I can verify the fix in our tests? |
Using fork of @pires manifests,@jimmidyson. https://github.com/porchdotcom/kubernetes-elasticsearch-cluster |
Will be fixed in next fabric8 release train. |
When's the next fabric8 release? |
Fingers crossed this week. On 21:51, Tue, 12 May 2015 Mulloy Morrow notifications@github.com wrote:
|
Please, let me know when it gets cut so I can continue with #11. |
|
So #12 has been merged and should fix this. @jimmidyson will you cut a new release, please? |
So |
@pires @mulloymorrow 1.1.2 isn't out yet sorry - had some problems getting this synced to Maven central. I'm squeezing in service account auth too - will be ready very soon I promise! |
@jimmidyson that should be 1.2.0 then ;) |
@pires @mulloymorrow OK released 1.2.0, docker image available at Updated documentation, albeit sparsely ;) |
Awesome @jimmidyson. Thanks a lot. |
This can be closed. |
Following the deployment of an app with 2GB of memory usage, ES cannot be resized or deployed in k8s.
Following error when spinning up ES cluster in k8s:
The text was updated successfully, but these errors were encountered: