I am importing data from my MySQL database to ES cluster and sometimes have
the following error while updating (already imported) document (Url -
called URL, Request: post data, Error: response error, I removed all
private data from the request):
How are you importing your data? Have you changed the refresh interval, or
forcing a refresh before doing the updates?
On Monday, December 3, 2012 11:51:41 PM UTC-8, Marcin Dojwa wrote:
Hi,
I am importing data from my MySQL database to ES cluster and sometimes
have the following error while updating (already imported) document (Url -
called URL, Request: post data, Error: response error, I removed all
private data from the request):
I did not change the refresh interval and I am not forcing a refresh before
_update. As I can see eg. here
just makes the changes visible for search, but operations using
document id for updating should be able to find the document before the
refresh is done too. Am I wrong ?
How are you importing your data? Have you changed the refresh interval, or
forcing a refresh before doing the updates?
On Monday, December 3, 2012 11:51:41 PM UTC-8, Marcin Dojwa wrote:
Hi,
I am importing data from my MySQL database to ES cluster and sometimes
have the following error while updating (already imported) document (Url -
called URL, Request: post data, Error: response error, I removed all
private data from the request):
I would have expected it to make the document available (for both search
and update), but I could be wrong.
How are you importing your data? Any chance that you're doing bulk inserts
and then not finishing the last bulk request? What client are you using?
On Tuesday, December 4, 2012 1:39:36 PM UTC-8, Marcin Dojwa wrote:
I did not change the refresh interval and I am not forcing a refresh
before _update. As I can see eg. here Elasticsearch Platform — Find real-time answers at scale | Elastic just makes the changes visible for search, but operations using
document id for updating should be able to find the document before the
refresh is done too. Am I wrong ?
How are you importing your data? Have you changed the refresh interval,
or forcing a refresh before doing the updates?
On Monday, December 3, 2012 11:51:41 PM UTC-8, Marcin Dojwa wrote:
Hi,
I am importing data from my MySQL database to ES cluster and sometimes
have the following error while updating (already imported) document (Url -
called URL, Request: post data, Error: response error, I removed all
private data from the request):
I do the bulk inserts using curl from command line. I wait untill this curl
requests finishes and then I resume indexing from my service. I do the bulk
like this:
curl -s -XPOST localhost:9200/_bulk --data-binary @<bulk_data_file> >
/dev/null
when the command above finishes I resume real time indexing and then
sometimes (very rare) I get this error.
I would have expected it to make the document available (for both search
and update), but I could be wrong.
How are you importing your data? Any chance that you're doing bulk inserts
and then not finishing the last bulk request? What client are you using?
On Tuesday, December 4, 2012 1:39:36 PM UTC-8, Marcin Dojwa wrote:
I did not change the refresh interval and I am not forcing a refresh
before _update. As I can see eg. here http://www.elasticsearch.**
org/guide/reference/api/admin-**indices-refresh.htmlhttp://www.elasticsearch.org/guide/reference/api/admin-indices-refresh.htmlrefreshing just makes the changes visible for search, but operations using
document id for updating should be able to find the document before the
refresh is done too. Am I wrong ?
How are you importing your data? Have you changed the refresh interval,
or forcing a refresh before doing the updates?
On Monday, December 3, 2012 11:51:41 PM UTC-8, Marcin Dojwa wrote:
Hi,
I am importing data from my MySQL database to ES cluster and sometimes
have the following error while updating (already imported) document (Url -
called URL, Request: post data, Error: response error, I removed all
private data from the request):
OK, it's not rare, if that happens for a specified alias (single client)
after importing its data to ES (using bulk) there are about 10-20 such
errors for this single alias within about 30 minutes. So it's NOT only
right after the bulk indexing is done.
I do the bulk inserts using curl from command line. I wait untill this
curl requests finishes and then I resume indexing from my service. I do the
bulk like this:
curl -s -XPOST localhost:9200/_bulk --data-binary @<bulk_data_file> >
/dev/null
when the command above finishes I resume real time indexing and then
sometimes (very rare) I get this error.
I would have expected it to make the document available (for both search
and update), but I could be wrong.
How are you importing your data? Any chance that you're doing bulk
inserts and then not finishing the last bulk request? What client are you
using?
On Tuesday, December 4, 2012 1:39:36 PM UTC-8, Marcin Dojwa wrote:
I did not change the refresh interval and I am not forcing a refresh
before _update. As I can see eg. here http://www.elasticsearch.**
org/guide/reference/api/admin-**indices-refresh.htmlhttp://www.elasticsearch.org/guide/reference/api/admin-indices-refresh.htmlrefreshing just makes the changes visible for search, but operations using
document id for updating should be able to find the document before the
refresh is done too. Am I wrong ?
How are you importing your data? Have you changed the refresh interval,
or forcing a refresh before doing the updates?
On Monday, December 3, 2012 11:51:41 PM UTC-8, Marcin Dojwa wrote:
Hi,
I am importing data from my MySQL database to ES cluster and sometimes
have the following error while updating (already imported) document (Url -
called URL, Request: post data, Error: response error, I removed all
private data from the request):
Blerg :-/ That's odd. I'd expect the implicit refresh to be called at that
point. Could you post a gist of the response you're getting from the bulk
request?
On Thursday, December 6, 2012 3:08:17 AM UTC-8, Marcin Dojwa wrote:
OK, it's not rare, if that happens for a specified alias (single client)
after importing its data to ES (using bulk) there are about 10-20 such
errors for this single alias within about 30 minutes. So it's NOT only
right after the bulk indexing is done.
I do the bulk inserts using curl from command line. I wait untill this
curl requests finishes and then I resume indexing from my service. I do the
bulk like this:
curl -s -XPOST localhost:9200/_bulk --data-binary @<bulk_data_file> >
/dev/null
when the command above finishes I resume real time indexing and then
sometimes (very rare) I get this error.
I would have expected it to make the document available (for both search
and update), but I could be wrong.
How are you importing your data? Any chance that you're doing bulk
inserts and then not finishing the last bulk request? What client are you
using?
On Tuesday, December 4, 2012 1:39:36 PM UTC-8, Marcin Dojwa wrote:
I did not change the refresh interval and I am not forcing a refresh
before _update. As I can see eg. here http://www.elasticsearch.**
org/guide/reference/api/admin-**indices-refresh.htmlhttp://www.elasticsearch.org/guide/reference/api/admin-indices-refresh.htmlrefreshing just makes the changes visible for search, but operations using
document id for updating should be able to find the document before the
refresh is done too. Am I wrong ?
How are you importing your data? Have you changed the refresh interval,
or forcing a refresh before doing the updates?
On Monday, December 3, 2012 11:51:41 PM UTC-8, Marcin Dojwa wrote:
Hi,
I am importing data from my MySQL database to ES cluster and
sometimes have the following error while updating (already imported)
document (Url - called URL, Request: post data, Error: response error, I
removed all private data from the request):
Unfortunatelly I do not have the responses from bulk indexing (I do not log
them). But this can be helpful I will do the response logging to be able
to check the logs for the aliases that fails.
Blerg :-/ That's odd. I'd expect the implicit refresh to be called at that
point. Could you post a gist of the response you're getting from the bulk
request?
On Thursday, December 6, 2012 3:08:17 AM UTC-8, Marcin Dojwa wrote:
OK, it's not rare, if that happens for a specified alias (single client)
after importing its data to ES (using bulk) there are about 10-20 such
errors for this single alias within about 30 minutes. So it's NOT only
right after the bulk indexing is done.
I do the bulk inserts using curl from command line. I wait untill this
curl requests finishes and then I resume indexing from my service. I do the
bulk like this:
curl -s -XPOST localhost:9200/_bulk --data-binary @<bulk_data_file> >
/dev/null
when the command above finishes I resume real time indexing and then
sometimes (very rare) I get this error.
I would have expected it to make the document available (for both search
and update), but I could be wrong.
How are you importing your data? Any chance that you're doing bulk
inserts and then not finishing the last bulk request? What client are you
using?
On Tuesday, December 4, 2012 1:39:36 PM UTC-8, Marcin Dojwa wrote:
I did not change the refresh interval and I am not forcing a refresh
before _update. As I can see eg. here http://www.elasticsearch.****
org/guide/reference/api/admin-****indices-refresh.htmlhttp://www.elasticsearch.org/guide/reference/api/admin-indices-refresh.htmlrefreshing just makes the changes visible for search, but operations using
document id for updating should be able to find the document before the
refresh is done too. Am I wrong ?
How are you importing your data? Have you changed the refresh
interval, or forcing a refresh before doing the updates?
On Monday, December 3, 2012 11:51:41 PM UTC-8, Marcin Dojwa wrote:
Hi,
I am importing data from my MySQL database to ES cluster and
sometimes have the following error while updating (already imported)
document (Url - called URL, Request: post data, Error: response error, I
removed all private data from the request):
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.