Also the kernel complains about too many connections being made at
once on the joining node.
(Seems to occur after 30 nodes joined the cluster)

TCP: TCP: Possible SYN flooding on port 9300. Sending cookies.  Check
SNMP counters.

On Fri, Feb 21, 2014 at 6:44 PM, Thibaut Britz <t.br...@trendiction.com> wrote:
> Hi,
>
> I'm working with Michel on that issue:
>
> The cluster is completely empty and has no indexes at all. So it certainly
> is not related to revocery.
> The old elasticsearch version doesn't have code to wait for replies which
> causes the very slow startup.
>
> Thanks,
> Thibaut
>
>
>
>
>
> On Fri, Feb 21, 2014 at 6:11 PM, Binh Ly <b...@hibalo.com> wrote:
>>
>> You may be interested in some settings that help a full cluster restart:
>>
>>
>> http://www.elasticsearch.org/guide/en/elasticsearch/reference/current/modules-gateway.html#recover-after
>>
>> There is also a webinar that talks about some of the above:
>>
>> http://www.elasticsearch.org/webinars/elasticsearch-pre-flight-checklist/
>>
>> --
>> 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+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/elasticsearch/a405d32a-50a5-4d83-a3c7-8a0ea3449d28%40googlegroups.com.
>>
>> For more options, visit https://groups.google.com/groups/opt_out.
>
>

-- 
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/elasticsearch/CAH0sEYjyTwFZFP7ZPCsOquSJDrYmdTrrhkmpD5XxbKpv-YO85A%40mail.gmail.com.
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to