hi,
whats the best way to copy all the ES indexes in my node to another mounted
drive, lets say?
my filesystem on which ES installation, data and log files are present got
corrupted. i want to unmount and run fsck on it and i dont know how long it
will take. meanwhile, i want to prevent service outage. so i want to copy
all of the data and binaries to another volume and start serving data from
there.
what are my options?
assuming that ill stop indexing while i am copying data, is that good
enough?
i just did a dd of my drive to another volume while ES was running (but no
indexing happening). but when i fired up the ES in the destination volume,
it didnt work as i got bunch of "NoShardAvailableActionException exceptions.
thanks
Hi,
I haven't tried it, but as far as I understand from here:
http://elasticsearch-users.115913.n3.nabble.com/ES-Backup-and-Restore-td3740144.html
you only need to disable flush and copy the data folder. Then you need to
change the config so that it gets the data from the new location. That
depends on how you have your ES installed. For example, if you installed it
on Ubuntu/Debian from the .deb package, you need to change "DATA_DIR" from
/etc/default/elasticsearch
On Wednesday, July 11, 2012 12:57:49 AM UTC+3, T Vinod Gupta wrote:
hi,
whats the best way to copy all the ES indexes in my node to another
mounted drive, lets say?
my filesystem on which ES installation, data and log files are present got
corrupted. i want to unmount and run fsck on it and i dont know how long it
will take. meanwhile, i want to prevent service outage. so i want to copy
all of the data and binaries to another volume and start serving data from
there.
what are my options?
assuming that ill stop indexing while i am copying data, is that good
enough?
i just did a dd of my drive to another volume while ES was running (but no
indexing happening). but when i fired up the ES in the destination volume,
it didnt work as i got bunch of "NoShardAvailableActionException exceptions.
thanks