ES seems to be stuck in resyncing mappings


(lukeforehand-2) #1

I am revisiting this archived thread:
http://groups.google.com/a/elasticsearch.com/group/users/browse_thread/thread/fe64dd72d233b1f7/30d8df648ae32beb?lnk=gst&q=ES+seems+to+be+stuck+in+resyncing+mappings#30d8df648ae32beb

I have gisted my log here:

We are also experiencing this problem with version 0.17.6

Does anyone have any insight as to how this can happen?

-Luke


(Shay Banon) #2

Is it something you can easily recreate? Can you post your mappings
definition for "default"?

On Thu, Aug 18, 2011 at 5:33 PM, lukeforehand lukeforehand@gmail.comwrote:

I am revisiting this archived thread:

http://groups.google.com/a/elasticsearch.com/group/users/browse_thread/thread/fe64dd72d233b1f7/30d8df648ae32beb?lnk=gst&q=ES+seems+to+be+stuck+in+resyncing+mappings#30d8df648ae32beb

I have gisted my log here:
https://gist.github.com/1152872

We are also experiencing this problem with version 0.17.6

Does anyone have any insight as to how this can happen?

-Luke


(lukeforehand-2) #3

It is easy to re-create, we don't run into this problem when indexing
to a single index. This seems to happen if several indices are being
created in a burst.

Here is the default mapping def:

-Luke

On Aug 18, 11:24 am, Shay Banon kim...@gmail.com wrote:

Is it something you can easily recreate? Can you post your mappings
definition for "default"?

On Thu, Aug 18, 2011 at 5:33 PM, lukeforehand lukeforeh...@gmail.comwrote:

I am revisiting this archived thread:

http://groups.google.com/a/elasticsearch.com/group/users/browse_threa...

I have gisted my log here:
https://gist.github.com/1152872

We are also experiencing this problem with version 0.17.6

Does anyone have any insight as to how this can happen?

-Luke


(Shay Banon) #4

Can you post a sample curl indexing that recreates it? I assume that just
starting two nodes, with the below configuration and indexing a doc causes
that?

On Thu, Aug 18, 2011 at 7:43 PM, lukeforehand lukeforehand@gmail.comwrote:

It is easy to re-create, we don't run into this problem when indexing
to a single index. This seems to happen if several indices are being
created in a burst.

Here is the default mapping def:

http://gist.github.com/1154470

-Luke

On Aug 18, 11:24 am, Shay Banon kim...@gmail.com wrote:

Is it something you can easily recreate? Can you post your mappings
definition for "default"?

On Thu, Aug 18, 2011 at 5:33 PM, lukeforehand <lukeforeh...@gmail.com
wrote:

I am revisiting this archived thread:

http://groups.google.com/a/elasticsearch.com/group/users/browse_threa.
..

I have gisted my log here:
https://gist.github.com/1152872

We are also experiencing this problem with version 0.17.6

Does anyone have any insight as to how this can happen?

-Luke


(Shay Banon) #5

I did not manage to recreate it, but I think I found where it might happen.
Pushed a fix: https://github.com/elasticsearch/elasticsearch/issues/1257(its
on 0.17 branch as well). Can you check it if helps?

On Thu, Aug 18, 2011 at 7:56 PM, Shay Banon kimchy@gmail.com wrote:

Can you post a sample curl indexing that recreates it? I assume that just
starting two nodes, with the below configuration and indexing a doc causes
that?

On Thu, Aug 18, 2011 at 7:43 PM, lukeforehand lukeforehand@gmail.comwrote:

It is easy to re-create, we don't run into this problem when indexing
to a single index. This seems to happen if several indices are being
created in a burst.

Here is the default mapping def:

http://gist.github.com/1154470

-Luke

On Aug 18, 11:24 am, Shay Banon kim...@gmail.com wrote:

Is it something you can easily recreate? Can you post your mappings
definition for "default"?

On Thu, Aug 18, 2011 at 5:33 PM, lukeforehand <lukeforeh...@gmail.com
wrote:

I am revisiting this archived thread:

http://groups.google.com/a/elasticsearch.com/group/users/browse_threa.
..

I have gisted my log here:
https://gist.github.com/1152872

We are also experiencing this problem with version 0.17.6

Does anyone have any insight as to how this can happen?

-Luke


(lukeforehand-2) #6

Thanks Shay, we have patched and will test today.

On Aug 18, 1:15 pm, Shay Banon kim...@gmail.com wrote:

I did not manage to recreate it, but I think I found where it might happen.
Pushed a fix:https://github.com/elasticsearch/elasticsearch/issues/1257(its
on 0.17 branch as well). Can you check it if helps?


(lukeforehand-2) #7

We have been testing with the patch for this and cannot reproduce the
problem. More testing to follow, will keep you posted. Thanks,

-Luke

On Aug 19, 9:02 am, lukeforehand lukeforeh...@gmail.com wrote:

Thanks Shay, we have patched and will test today.

On Aug 18, 1:15 pm, Shay Banon kim...@gmail.com wrote:

I did not manage to recreate it, but I think I found where it might happen.
Pushed a fix:https://github.com/elasticsearch/elasticsearch/issues/1257(its
on 0.17 branch as well). Can you check it if helps?


(Shay Banon) #8

Great, thanks for the update!

On Mon, Aug 22, 2011 at 9:48 PM, lukeforehand lukeforehand@gmail.comwrote:

We have been testing with the patch for this and cannot reproduce the
problem. More testing to follow, will keep you posted. Thanks,

-Luke

On Aug 19, 9:02 am, lukeforehand lukeforeh...@gmail.com wrote:

Thanks Shay, we have patched and will test today.

On Aug 18, 1:15 pm, Shay Banon kim...@gmail.com wrote:

I did not manage to recreate it, but I think I found where it might
happen.

Pushed a fix:
https://github.com/elasticsearch/elasticsearch/issues/1257(its

on 0.17 branch as well). Can you check it if helps?


(system) #9