Le 10 mai 2013 à 10:21, David Pilato david@pilato.fr a écrit :
What does "_ttl" : -23976963 mean?
I think that the 'error' comes from here.
It was my first though, but as the delete query works, so internal ttl values are correct
-23976963 is just a long displayed as int afaik
My 2 cents.
--
David
Twitter : @dadoonet / @elasticsearchfr / @scrutmydocsLe 10 mai 2013 à 10:06, Stéphane Cottin vixnsgm@gmail.com a écrit :
I was wrong, java update did not fix anything.
ttl cleaning seems broken in 0.90.
running with debug log level show purge loops are fired, but they don't delete anything.as a workaround, i'm running a cron job once per hour :
#!/bin/sh
curl -XDELETE http://127.0.0.1:9200/graylog2_recent/_query -d "{"range":{"_ttl":{"to":$(date +%s)000}}}"
curl http://127.0.0.1:9200/graylog2_recent/_optimizenot elegant, but works
Le mercredi 8 mai 2013 10:04:15 UTC+2, Stéphane Cottin a écrit :
upgrade from openjdk 6 to openjdk 7 fix it.Le lundi 6 mai 2013 09:25:59 UTC+2, Stéphane Cottin a écrit :
Hi,I'm using ES 0.90 with graylog2, expired documents in recent index are not purged.
appear ES related to me, is this a bug or a misconfiguration ?
how can i manually purge old entries ?thx
_settings :
{
"graylog2_recent" : {
"settings" : {
"index.store.type" : "niofs",
"index.number_of_replicas" : "0",
"index.number_of_shards" : "4",
"index.version.created" : "900099"
}
}
}_mapping :
{
"graylog2_recent" : {
"message" : {
"dynamic_templates" : [ {
"store_generic" : {
"mapping" : {
"index" : "not_analyzed"
},
"match" : "*"
}
} ],
"_ttl" : {
"enabled" : true
},
"_source" : {
"compress" : true
},
[...][...]/graylog2_recent/_search?pretty=true&fields=_ttl,_timestamp
{
"took" : 8,
"timed_out" : false,
"_shards" : {
"total" : 4,
"successful" : 4,
"failed" : 0
},
"hits" : {
"total" : 463837,
"max_score" : 1.0,
"hits" : [ {
"_index" : "graylog2_recent",
"_type" : "message",
"_id" : "bfbebd30-b5db-11e2-aecd-00163e783829",
"_score" : 1.0,
"fields" : {
"_ttl" : -23976963,
"_timestamp" : "06/May/2013:01:30:19 +0200"
}
}, {
"_index" : "graylog2_recent",
"_type" : "message",
"_id" : "bfcbb580-b5db-11e2-aecd-00163e783829",
"_score" : 1.0,
"fields" : {
"_ttl" : -23976878,
"_timestamp" : "06/May/2013:01:30:19 +0200"
}
}, {
"_index" : "graylog2_recent",
"_type" : "message",
"_id" : "bfd37db0-b5db-11e2-aecd-00163e783829",
"_score" : 1.0,
"fields" : {
"_ttl" : -23976828
}
}, {
"_index" : "graylog2_recent",
"_type" : "message",
"_id" : "bfeaaf30-b5db-11e2-aecd-00163e783829",
"_score" : 1.0,
"fields" : {
"_ttl" : -23976675,
"_timestamp" : "06/May/2013:01:30:19 +0200"
}
}, {
[...]--
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.--
You received this message because you are subscribed to a topic in the Google Groups "elasticsearch" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/elasticsearch/RALBkPjLgac/unsubscribe?hl=en-US.
To unsubscribe from this group and all its topics, send an email to elasticsearch+unsubscribe@googlegroups.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 elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.