If you haven't already, see:
In general, I would advise against doing automated updating unless you have
a significantly large cluster size. Mostly because nothing is guaranteed
version to version and there might be caveats for new releases you might
not be aware of before your cluster has already started the process. It
would be very simple for something to go wrong that might affect data
integrity and/or cluster stability.
If you must proceed down this route, create a small staging/test cluster w/
data and test the upgrade there first. Hopefully you're using VMs so you
can snapshot and observe your upgrade's behavior before affecting
Note: If you were thinking of updating a node in-place, you should instead
try symlinking the production ES service so you can then (1) download the
new version, (2) stop shard allocation and ES, (3) update/change the
symlink, and (4) restart ES. Also covered in the link above.
On Monday, August 11, 2014 1:39:24 PM UTC-5, kti...@hotmail.com wrote:
I am very new to Elastic Search. I was curious if ES service can
periodically check for the latest version such as 1.1.3 and update nodes
one at a time silently?
I am in the process of writing PowerShell script to do this but thought
ES might have solution for this already.
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/e7b0953a-6853-4ba7-a63d-858ed2c93be9%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.