Hey,
did you have a huge amount of updates shortly before, when this strange
behaviour happens? One of the reasons you refresh is not executing, might
be because the refresh, which started a second earlier has not yet been
finished. But the refresh you are executing manually should not be
different.
If you force the refresh, how long does it take until the documents are
searchable? Immediately?
--Alex
On Tue, Jul 30, 2013 at 9:12 PM, Jeremy Karlson jeremykarlson@gmail.comwrote:
Hi Alex,
I apologize for the delay in getting back to you. We haven't seen this
behaviour in a while, so I had nothing to report. It came back again
today, so now I have something new to say.What we're seeing could be explained by what you're describing. We can
still insert documents without problem, and look them up directly by ID,
but doing a query does not find them, even if you wait 10 seconds or more.
After we force the index to refresh, the documents appear in query results.At the time, we hadn't tinkered with any refresh or translog settings.
But now we have now tried changing the index:refresh_interval setting. We
tried changing it to "2s" just to see if it made any difference or somehow
woke up the indexer. It didn't have any effect.-- Jeremy
On Monday, July 15, 2013 11:40:51 PM UTC-7, Alexander Reelsen wrote:
Hi,
this sounds strange. Can you execute a refresh or a flush manually next
time it happens? See
Elasticsearch Platform — Find real-time answers at scale | Elastic**
indices-refresh/http://www.elasticsearch.org/guide/reference/api/admin-indices-refresh/
Elasticsearch Platform — Find real-time answers at scale | Elastichttp://www.elasticsearch.org/guide/reference/api/admin-indices-flush/It sounds as if your data is stored in the translog (which makes it
durable and accessible by ID) but never gets committed to the index (which
makes it searchable). Also you long recovery times might come from the
fact, that the hugely filled translog is written into the index
(speculating right now, but might rexplain your recovery behaviour)Did you change any refresh settings, any translog settings?
--Alex
On Tue, Jul 16, 2013 at 2:51 AM, Jeremy Karlson jeremy...@gmail.comwrote:
I experienced this behaviour again. It doesn't happen to just one
document, it appears that after a while ES continues to receive changes
(new docs / updates / deletes), but no changes never appear to become
visible. If you restart ES, they all appear.Still running 0.90.1.
-- Jeremy
On Thursday, 27 June 2013 14:28:47 UTC-7, Jeremy Karlson wrote:
I ran your sample. No, I don't get the same errors I did earlier.
But, I didn't expect to... I mentioned earlier that the problem "went
away" when I restarted Elasticsearch to turn up the logging. Since then (a
day or two ago) things have been running well.And yeah, I'm running 0.90.1.
Thanks.
-- Jeremy
On Wednesday, 26 June 2013 23:42:28 UTC-7, Alexander Reelsen wrote:
Hey,
if you run my sample, do you encounter the same errors (maybe I did a
mistake when converting your queries)?
Then, what version of elasticsearch are you using (I tried with
0.90.1)?--Alex
--
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 elasticsearc...@**googlegroups.com.For more options, visit https://groups.google.com/**groups/opt_outhttps://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.
--
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.