I'm doing next test...
When I come today morning cluster finished shards allocation (status
green). I run next load (indexing) and everything finished correctly. After
that I stoped all cluster nodes and run them again. Nodes started shards
allocation. In that time all thread pools were free:
o1 10.13.186.100 0 0 0 0 0 0 0 0 0
o2 10.13.186.110 0 0 0 0 0 0 0 0 0
h1 10.14.180.41 0 0 0 0 0 0 0 0 0
h2 10.14.180.42 0 0 0 0 0 0 0 0 0
h3 10.14.180.43 0 0 0 0 0 0 0 0 0
h4 10.14.180.44 0 0 0 0 0 0 0 0 0
h5 10.14.180.45 0 0 0 0 0 0 0 0 0
h6 10.14.180.46 0 0 0 0 0 0 0 0 0
In next step I created indexs - finished OK. After that I started update
mapping but I have error:
1. perl Search::Elasticsearch
[Timeout] ** [http://h1:9200]-[509] 28: Timeout was reached, called from
sub Search::Elasticsearch::Transport::try {...} at
/usr/local/share/perl5/Try/Tiny.pm line 81. With vars: {'request' =>
{'body' => {'schema' => {'properties' => .... 'qs' => {},'method' =>
'PUT','serialize' => 'std','path' =>
'/new_index_name/_mapping/schema','ignore' => [],'mime_type' =>
'application/json'},'status_code' => 509}
2. curl
{"error":"RemoteTransportException[[o2][inet[/10.13.186.110:9300]][indices:admin/mapping/put]];
nested: ProcessClusterEventTimeoutException[failed to process cluster event
(put-mapping [schema]) within 30s]; ","status":503}
During shards allocation some cluster resources are full utilized, but I
don't have idea witch one. It's interesing that I can create new index but
I can't update mapping.
Any suggestion?
Regards
W dniu środa, 14 stycznia 2015 20:06:31 UTC+1 użytkownik Marek Dabrowski
napisał:
>
> David
>
> Before I started migration I checked many records counter - 1000, 2000,
> 5000, 100 000, etc. Im my configuration 200 000 is optimal value. Problem
> with timeout is not directly conected with quantity of records because now
> I stoped all load (indexing) processes and I can't update mapping for new
> indexes. Cluster now is during shards allocation process after restart. I'm
> trying create new one and update appropriate mapping for it. I do it by
> pure curl request and by perl Search::Elasticsearch with all option for cxn
> (NetCurl, LWP, etc.) but cluster still answare that after 30s with
> exception that update mapping isn't possible. I think that this problem is
> conected with some parameters for buffers, queues (?), but I don't know
> what.
>
> Regards
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/elasticsearch/5ab6d96f-e5cc-4ce1-b528-acedccef7ccf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
