Thank you for the answer, but may I know why? What is the reason behind
this?
thanks,
Domonkos
2014.09.18. 16:15 keltezéssel, David Pilato írta:
Only metadata are compressed.
--
David ;-)
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocs
Le 18 sept. 2014 à 15:36, "Tomcsányi, Domonkos" <[email protected]> a écrit :
Hi Everyone,
I just started experimenting with the cool snapshot feature of ES (using ES
1.3.2 on Ubuntu 14.04) using curator. I created a new repository on a mounted
NFS storage, using only the default options (compression turned on). I checked
it using curl:
user@myserver:~# curl -XGET 'http://IP_ADDRESS:9200/_snapshot/logBack?pretty'
{
"logBack" : {
"type" : "fs",
"settings" : {
"compress" : "true",
"location" : "/es_snapshots"
}
}
}
So, after that I used curator to create a snapshot of some older indices. The
process finished after some minutes, so I decided to have a look at the files
it created. It turned out that the snapshot's files take up exactly as much
space as the indices did originally while they were in the cluster, so no
compression happened at all. This is kind of a problem for me, because I
assumed that compression will greatly reduce the size of the indices I put in a
snapshot. So is there anything I'm doing wrong?
Thank you,
Domonkos
--
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/541ADFEF.7080800%40modit.hu.
For more options, visit https://groups.google.com/d/optout.
--
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/541AED9F.4030007%40modit.hu.
For more options, visit https://groups.google.com/d/optout.
