I currently run a forum with 1.4 million posts indexed by
Elasticsearch on XenForo.
The issue several of us are experiencing is very occasionally (maybe 1
or 2 times per day on my forum with about 1000-2000 searches per day)
a search result will come back with an empty result and generate the
error in the admin log of XenForo of
XenForo_Exception: Elasticsearch server returned no response. Is it
running? - library/XenES/Search/SourceHandler/ElasticSearch.php:721
However, as quickly as the error shows it it disappears, and
everything carries on. Now, I have caught the error once on my board,
and logging into SSH and checking the services showed ES was runing
away happily.
I thought maybe it could be due to some timeout or idle setting, that
the first search after X ammount of time that it just needs waking up
and that may be the first result, however we tried creating a cron
script to run the curl 127.0.0.1:9200 command as well as one handing
and actual search query to the service to keep it alive and if
anything it caused more errors.
However I believe this is now venturing out of my knowledge and skill
to locate the cause of the problem (as minimal as it is, we would
still like to resolve it!) so would like any suggestions you may have.
Did you see anything relevant in Elasticsearch's logs?
Also, it would be nice if you could find out what was the actual reply
from Elasticsearch, if any (eg: return code 500, connection refused,
connection timed out...).
I currently run a forum with 1.4 million posts indexed by
Elasticsearch on XenForo.
The issue several of us are experiencing is very occasionally (maybe 1
or 2 times per day on my forum with about 1000-2000 searches per day)
a search result will come back with an empty result and generate the
error in the admin log of XenForo of
XenForo_Exception: Elasticsearch server returned no response. Is it
running? - library/XenES/Search/SourceHandler/Elasticsearch.php:721
However, as quickly as the error shows it it disappears, and
everything carries on. Now, I have caught the error once on my board,
and logging into SSH and checking the services showed ES was runing
away happily.
I thought maybe it could be due to some timeout or idle setting, that
the first search after X ammount of time that it just needs waking up
and that may be the first result, however we tried creating a cron
script to run the curl 127.0.0.1:9200 command as well as one handing
and actual search query to the service to keep it alive and if
anything it caused more errors.
However I believe this is now venturing out of my knowledge and skill
to locate the cause of the problem (as minimal as it is, we would
still like to resolve it!) so would like any suggestions you may have.
I have had a look and nothing seems to show up in logs.
I have enabled the commented out "gateway" log options to see if that helps.
On Tuesday, 6 March 2012 05:53:07 UTC, Radu Gheorghe wrote:
Hi,
Did you see anything relevant in Elasticsearch's logs?
Also, it would be nice if you could find out what was the actual reply
from Elasticsearch, if any (eg: return code 500, connection refused,
connection timed out...).
I currently run a forum with 1.4 million posts indexed by
Elasticsearch on XenForo.
The issue several of us are experiencing is very occasionally (maybe 1
or 2 times per day on my forum with about 1000-2000 searches per day)
a search result will come back with an empty result and generate the
error in the admin log of XenForo of
XenForo_Exception: Elasticsearch server returned no response. Is it
running? - library/XenES/Search/SourceHandler/Elasticsearch.php:721
However, as quickly as the error shows it it disappears, and
everything carries on. Now, I have caught the error once on my board,
and logging into SSH and checking the services showed ES was runing
away happily.
I thought maybe it could be due to some timeout or idle setting, that
the first search after X ammount of time that it just needs waking up
and that may be the first result, however we tried creating a cron
script to run the curl 127.0.0.1:9200 command as well as one handing
and actual search query to the service to keep it alive and if
anything it caused more errors.
However I believe this is now venturing out of my knowledge and skill
to locate the cause of the problem (as minimal as it is, we would
still like to resolve it!) so would like any suggestions you may have.
It would be great to understand what the actual error is in the no response message. Is it a timeout (connect timeout, receive timeout), what is the error code that is returned if returned.
On Tuesday, March 6, 2012 at 2:56 AM, Slavik wrote:
Hi there guys,
I currently run a forum with 1.4 million posts indexed by
Elasticsearch on XenForo.
The issue several of us are experiencing is very occasionally (maybe 1
or 2 times per day on my forum with about 1000-2000 searches per day)
a search result will come back with an empty result and generate the
error in the admin log of XenForo of
XenForo_Exception: Elasticsearch server returned no response. Is it
running? - library/XenES/Search/SourceHandler/Elasticsearch.php:721
However, as quickly as the error shows it it disappears, and
everything carries on. Now, I have caught the error once on my board,
and logging into SSH and checking the services showed ES was runing
away happily.
I thought maybe it could be due to some timeout or idle setting, that
the first search after X ammount of time that it just needs waking up
and that may be the first result, however we tried creating a cron
script to run the curl 127.0.0.1:9200 command as well as one handing
and actual search query to the service to keep it alive and if
anything it caused more errors.
However I believe this is now venturing out of my knowledge and skill
to locate the cause of the problem (as minimal as it is, we would
still like to resolve it!) so would like any suggestions you may have.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.