Hi all,
I'm sure this is a question that gets asked a lot. I was able to find good
answers for rolling restarts, but that's more complicated than I really
need. I also had trouble finding specific references to APIs that should be
used. I'm hoping you can help me fill in the gaps.
I currently have an 8 node ElasticSearch cluster running version 0.20.2
containing 220 million or so log messages. I would like to upgrade this
cluster to 0.90.3. This isn't a critical service, so downtime is fine. I'd
still like to back up indexed data in case I need to roll back.
The process as I understand it:
- Stop indexing incoming documents via the admin indices open/close API.
- Flush each index using the admin indices flush API.
- (This one I'm not sure about) Disable shard allocation and/or set
mininum_master_nodes to 8 to prevent data from being shuffled around when
nodes come back up. - Shut down all nodes.
- Back up data by copying the data directory from each node somewhere
else. - Install new version of ElasticSearch.
- I'm gonna be using the debian package to install, so I'd just do a
dpkg -i and call it a day?
- I'm gonna be using the debian package to install, so I'd just do a
- Once the upgrade is complete, bring the cluster back up and hope that
all the nodes rejoin. - If nodes are having issues or if data is corrupt, reinstall 0.20.2
and hope things start working again. Possibly copy backups back to nodes.
Does this seem accurate? Am I missing anything?
Thanks for your time!
--
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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.