Aliasies Performance in Cluster


(LORDs_diakonos) #1

I have a question regarding adding/removing aliases. I am running in
a cluster and it seems to be slow to add and remove aliases and not
always finish
I am running the following code http://pastebin.com/rhrbs47V

is it normal for this to take a long time?

Also I notice that while that code is running I am getting a ton of
things like this in the log until it finally times out
INFO cluster.metadata: [dotCMS_1] [live_20120124102301] update_mapping
[content] (dynamic)

After this happens the second server came in and was able to make the
logic fire. Our code ensures only one server in the cluster can be in
this code at a time.

Thanks,
Jason Tesser
dotCMS Director, Support Services
1-305-858-1422


(Shay Banon) #2

Alias operations should not take a long time. Do you get a response at the
end? (just call actionGet() without a timeout). Settings aliases will not
cause for those update mapping to happen, but maybe once you changed it,
index operations now hit a fresh index where new (dynamic) mapping
definitions need to be applied?

On Tue, Jan 24, 2012 at 7:26 PM, Jason Tesser jasontesser@gmail.com wrote:

I have a question regarding adding/removing aliases. I am running in
a cluster and it seems to be slow to add and remove aliases and not
always finish
I am running the following code http://pastebin.com/rhrbs47V

is it normal for this to take a long time?

Also I notice that while that code is running I am getting a ton of
things like this in the log until it finally times out
INFO cluster.metadata: [dotCMS_1] [live_20120124102301] update_mapping
[content] (dynamic)

After this happens the second server came in and was able to make the
logic fire. Our code ensures only one server in the cluster can be in
this code at a time.

Thanks,
Jason Tesser
dotCMS Director, Support Services
1-305-858-1422


(LORDs_diakonos) #3

i got this

org.elasticsearch.ElasticSearchException: Timeout waiting for task.
at com.dotcms.content.elasticsearch.business.ESIndexAPI.fullReindexSwitchover(ESIndexAPI.java:324)
at com.dotmarketing.common.reindex.ReindexThread.run(ReindexThread.java:90)
Caused by: org.elasticsearch.ElasticSearchTimeoutException: Timeout
waiting for task.
at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:68)
at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:57)
at com.dotcms.content.elasticsearch.business.ESIndexAPI.fullReindexSwitchover(ESIndexAPI.java:301)

and it didn't finish

Thanks,
Jason Tesser
dotCMS Director, Support Services
1-305-858-1422

On Tue, Jan 24, 2012 at 12:35 PM, Shay Banon kimchy@gmail.com wrote:

Alias operations should not take a long time. Do you get a response at the
end? (just call actionGet() without a timeout). Settings aliases will not
cause for those update mapping to happen, but maybe once you changed it,
index operations now hit a fresh index where new (dynamic) mapping
definitions need to be applied?


(LORDs_diakonos) #4

We are setting some dynamic mappings. Would this cause an issue with
either adding OR removing aliases

Thanks,
Jason Tesser
dotCMS Director, Support Services
1-305-858-1422

On Tue, Jan 24, 2012 at 12:39 PM, Jason Tesser jasontesser@gmail.com wrote:

i got this

org.elasticsearch.ElasticSearchException: Timeout waiting for task.
at com.dotcms.content.elasticsearch.business.ESIndexAPI.fullReindexSwitchover(ESIndexAPI.java:324)
at com.dotmarketing.common.reindex.ReindexThread.run(ReindexThread.java:90)
Caused by: org.elasticsearch.ElasticSearchTimeoutException: Timeout
waiting for task.
at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:68)
at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:57)
at com.dotcms.content.elasticsearch.business.ESIndexAPI.fullReindexSwitchover(ESIndexAPI.java:301)

and it didn't finish

Thanks,
Jason Tesser
dotCMS Director, Support Services
1-305-858-1422

On Tue, Jan 24, 2012 at 12:35 PM, Shay Banon kimchy@gmail.com wrote:

Alias operations should not take a long time. Do you get a response at the
end? (just call actionGet() without a timeout). Settings aliases will not
cause for those update mapping to happen, but maybe once you changed it,
index operations now hit a fresh index where new (dynamic) mapping
definitions need to be applied?


(Shay Banon) #5

The timeout you see if because you specified a timeout on the actionGet method, can you try and not set it and see what you get? (the aliases API waits for ack from all the other nodes that it has been applied, it waits by default for 10 seconds).

What do you mean by setting more mappings?

On Tuesday, January 24, 2012 at 7:42 PM, Jason Tesser wrote:

We are setting some dynamic mappings. Would this cause an issue with
either adding OR removing aliases

Thanks,
Jason Tesser
dotCMS Director, Support Services
1-305-858-1422

On Tue, Jan 24, 2012 at 12:39 PM, Jason Tesser <jasontesser@gmail.com (mailto:jasontesser@gmail.com)> wrote:

i got this

org.elasticsearch.ElasticSearchException: Timeout waiting for task.
at com.dotcms.content.elasticsearch.business.ESIndexAPI.fullReindexSwitchover(ESIndexAPI.java:324)
at com.dotmarketing.common.reindex.ReindexThread.run(ReindexThread.java:90)
Caused by: org.elasticsearch.ElasticSearchTimeoutException: Timeout
waiting for task.
at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:68)
at org.elasticsearch.action.support.AdapterActionFuture.actionGet(AdapterActionFuture.java:57)
at com.dotcms.content.elasticsearch.business.ESIndexAPI.fullReindexSwitchover(ESIndexAPI.java:301)

and it didn't finish

Thanks,
Jason Tesser
dotCMS Director, Support Services
1-305-858-1422

On Tue, Jan 24, 2012 at 12:35 PM, Shay Banon <kimchy@gmail.com (mailto:kimchy@gmail.com)> wrote:

Alias operations should not take a long time. Do you get a response at the
end? (just call actionGet() without a timeout). Settings aliases will not
cause for those update mapping to happen, but maybe once you changed it,
index operations now hit a fresh index where new (dynamic) mapping
definitions need to be applied?


(system) #6