-Original Message-
From: Koji Kawamura [mailto:ijokaruma...@gmail.com]
Sent: lundi 13 février 2017 10:04
To: users@nifi.apache.org
Subject: Re: Cluster instability due to java.net.SocketTimeoutException: Read
timed out
Hello,
The timeout happens when a node replicate a request to nodes
ler.java:153)
> ~[jersey-client-1.19.jar:1.19]
> ... 12 common frames omitted
>
> perhaps it is useful to understand the problem.
>
>
>
>
> From: Alessio Palma <alessio.pa...@docomodigital.com>
> Sent: Monday, February 13, 201
: NIFI User mailing
Subject: Cluster instability due to java.net.SocketTimeoutException: Read timed
out
Hello all,
sometime the cluster is unstable due to "read time out".
Is here any parameter which I can fine tuning in order to reduce this problem ?
Most timeouts (66%)
Hello all,
sometime the cluster is unstable due to "read time out".
Is here any parameter which I can fine tuning in order to reduce this problem ?
Most timeouts (66%) are coming from
com.sun.jersey.api.client.ClientHandlerException
few (33%) from
o.apache.nifi.controller.FlowController
