Update with refresh flag not immediately refreshing


(Paul Bellora) #1

My application has a list of objects that are sorted by a timestampModifiedfield, descending - the results of this page are driven by ES queries.
These objects can be edited, and after saving an object it is expected to
appear at the top of the results. Because of this, I'm sending refresh=trueon the corresponding
update request. However, in some environments, the object is not updated in
time for page reload, and remains in the same spot.

Reading the updatehttp://www.elasticsearch.org/guide/reference/api/update/ documentation,
it says:

refresh: Refresh the index immediately after the operation occurs, so that

the updated document appears in search results immediately.

Does this guarantee the refresh has happened by the time the update
response is received? Or is it possible there is still a slight delay
happening here?

--
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.


(Adrien Grand) #2

Hi Paul,

On Thu, Aug 29, 2013 at 11:27 PM, Paul Bellora bellorap@gmail.com wrote:

My application has a list of objects that are sorted by a
timestampModified field, descending - the results of this page are driven
by ES queries. These objects can be edited, and after saving an object it
is expected to appear at the top of the results. Because of this, I'm
sending refresh=true on the corresponding update request. However, in
some environments, the object is not updated in time for page reload, and
remains in the same spot.

Reading the updatehttp://www.elasticsearch.org/guide/reference/api/update/ documentation,
it says:

refresh: Refresh the index immediately after the operation occurs, so

that the updated document appears in search results immediately.

Does this guarantee the refresh has happened by the time the update
response is received? Or is it possible there is still a slight delay
happening here?

There shouldn't be any delay, how easily can you reproduce the issue?

--
Adrien Grand

--
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.


(Paul Bellora) #3

This was due to a mistake that was made deploying to my test environment -
ES was behaving correctly. Sorry for the noise.

On Friday, August 30, 2013 4:09:29 AM UTC-4, Adrien Grand wrote:

Hi Paul,

On Thu, Aug 29, 2013 at 11:27 PM, Paul Bellora <bell...@gmail.com<javascript:>

wrote:

My application has a list of objects that are sorted by a
timestampModified field, descending - the results of this page are
driven by ES queries. These objects can be edited, and after saving an
object it is expected to appear at the top of the results. Because of this,
I'm sending refresh=true on the corresponding update request. However,
in some environments, the object is not updated in time for page reload,
and remains in the same spot.

Reading the updatehttp://www.elasticsearch.org/guide/reference/api/update/ documentation,
it says:

refresh: Refresh the index immediately after the operation occurs, so

that the updated document appears in search results immediately.

Does this guarantee the refresh has happened by the time the update
response is received? Or is it possible there is still a slight delay
happening here?

There shouldn't be any delay, how easily can you reproduce the issue?

--
Adrien Grand

--
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.


(system) #4