Hi Tony,
The problem is the hardware, that is why we need to move it to the new
cluster.
Yann, how can I restore a snapshot on a different machine?
Cheers,
Attila
On 02/19/2014 07:00 PM, Tony Su wrote:
I was wondering which backup/restore method you intended to use.
Snapshot/restore requires 1.0.
If you intend to upgrade your 0.9.x cluster to 1.0 first, it looks like
possibly a really good option (I intend to start testing
snapshot/restore sometime soon. I've already created snapshots and am
impressed how it seems to take roughly the same amount to create a
snapshot no matter how much data is being backed up, probably within reason)
If your chosen path requires upgrading the existing cluster to 1.0
anyway, why migrate to the new cluster?
Tony
On Wednesday, February 19, 2014 8:16:02 AM UTC-8, Attila Bukor wrote:
Hi Yann,
Thank you for your response, you saved me from a *lot* of headache.
So the
revised flow:
- Upgrade oldcluster to 1.0.0.
- Implement a logger in the application which dumps all index API calls
into a file.
- Backup my index on oldcluster following these docs:
http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/modules-snapshots.html
<http://www.elasticsearch.org/guide/en/elasticsearch/reference/master/modules-snapshots.html>
- Restore the backed up index on newcluster following the same docs.
- Run the log from after the last _id in the snapshot. Repeat until
they're the same.
- Change the IP to newcluster in the application.
- Repeat step 5 one more time.
- Remove logging, delete logs.
- Shut down oldcluster.
In this case, the switch should not be noticed by anyone and the data
integrity is guaranteed, right?
Cheers,
Attila
On Wed, 19 Feb 2014, Yann Barraud wrote:
> Hi,
>
> If I get you well, you'll face an issue. Renaming oldcluster will
make it "forget" previous indexes. (Take a look at data you'll find a
dir named "oldcluster").
>
> The step you're missing is to backup data fro oldcluster
> Then shtudown, rename
> Then restore...
>
> Or even shutdown and restore on new cluster...
>
> Cheers,
> Yann
>
>
>
> Le mercredi 19 février 2014 16:01:03 UTC+1, Attila Bukor a écrit :
> Hey everybody,
>
> I have a question regarding the migration of the indices to a
new cluster
> seamlessly. Let me first describe the situation:
>
> I have a project which uses Elasticsearch since a few weeks
ago. This is our
> first Elasticsearch project, and as we are satisfied with it,
we decided to
> dedicate a cluster of 3 nodes to run Elasticsearch (lets
call it
> "newcluster"). It is up and running separately from our old
1-node
> Elasticsearch installation ("oldcluster"). We want to migrate
everything to
> newcluster, and turn oldcluster off. All 4 servers are running
Ubuntu Server,
> Elasticsearch is installed from the official deb package,
oldcluster is
> 0.90.10 and newcluster 1.0.0.
>
> I came up with the following solution, but I'm not sure it
will
work:
>
> - Upgrade oldcluster to 1.0.0 (tested it in dev, should work)
> - Backup the index (we have only one index right now) in case
something goes
> wrong.
> - Change oldcluster's name to newcluster.
> - Wait until the nodes synchronize themselves (how can I check
if they're in
> sync?)
> - Shut down oldcluster.
>
> Thank you very much,
> Attila
>
>
>
--
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 protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/f375faef-2dd4-416d-8150-75afe2318f0c%40googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
--
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 protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/le4ne3%24cg5%241%40ger.gmane.org.
For more options, visit https://groups.google.com/groups/opt_out.
