Apologies if this is a silly question.
I recently changed the disk layout on one of my ES nodes to put
/var/lib/elasticsearch on it's own disk partition. Around 100Gb data was
set to one side, new disk created, then rsync'd to it's new partition.
As far as I can be certain, everything was the same before and after the
operation - just that the data now sat on it's own partition. Ownership,
permissions, ACL's, SELinux contexts were all synced.
When I started elasticsearch back up again, however, the 100Gb in the
partition vanished and the node started to rebuild itself from scratch,
copying data in from all the other nodes.
The time between stopping and restarting elasticsearch was around 15
minutes. I expected the data that I'd put back in place to be used first
as most of it is historical and won't have changed.
Did I do something wrong in my procedure, or am I just expecting the wrong
I'm hoping that doing disk maintenance like this in a production system
doesn't trigger such a rebuild as my prod systems will have significantly
RHEL 6.5 x86_64
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/e0a204a7-318b-447b-8fcb-7955559b5a3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.