Elasticsearch 2.0
Opened this issue · 4 comments
I am currently playing around with the ES template attempting to get 2.0.0 up and running. I changed all the ES images to use 2.0.0 but the stack seems to get stuck in an upgrading service loop when I bring it up and I'm not sure where to start troubleshooting. Any ideas?
Ah, I was wondering if anyone was going to try this. The 0.1.0, 0.2.0 and 0.3.0 templates were all built before upgrade was added to Rancher, and are not really set up to do so. The 0.2.1 and 0.3.1 tags are the ones that can upgrade easily.
If you need to upgrade 0.1.0, it is possible and we have to do it ourselves at some point, its going to be more involved because it was using DNS instead of metadata.
@cloudnautique I apologize, my original description wasn't very good. I cloned this repo and manually changed the references in the 0.3.1 directory to use image:elasticsearch:2.0.0 instead of 1.7.3 to get the stack created and eventually to the broken state.
This was bringing up the stack from scratch as I wasn't actually trying to upgrade from a different version.
Gotcha :)
I hadn't seen Elasticsearch 2.0 went GA. I'll have to take a look at the images to see whats going on.
I've issued a pull request for rancher catalog templates that run elasticsearch/kopf v2.1.1 and kibana v4.3.1. I'm waiting for those to be merged then I will issue one for the latest logstash.
If you want to try them out, check out the repo mgolly/rancher-catalog-dev.