Hi Yun,
You mean, we need to increase the connections in connection pool ?. We dint
have any changes to our code before upgrade. Same code is working on 4.7
version.
Note : We are using APACHE_PHOENIX-4.11.0-cdh5.11.2.p0.1.
Thanks,
Anil
On 24 March 2018 at 20:57, zhang yun
Hi, Anil.
It seems that this exception is not bug, you should check your code of
logical layer. Sometimes this exception will be trigger when multiple
thread to access connections pool( some connections are closed at that
time).
Yun Zhang
Best
Hi Josh,
i didn't find any other exception. i will check again. Exceptions happened
only on few nodes. i have seen failed to get regions exception on few
nodes. I will check agian and comeback to more details. Thanks.
Regards,
Anil
On 22 March 2018 at 21:56, Josh Elser
Hey Anil,
You sure there isn't another exception earlier on in the output of your
application? The exception you have here looks more like the JVM was
already shutting down and Phoenix had closed the connection (the
exceptions were about queued tasks being cleared out after the decision
to
HI Team,
We have upgraded the phoenix from 4.7.0 to 4.11.0 and started noticing the
attached exception.
Can you help me identifying the root cause of the exception ? Thanks.
Regards,
Anil
2018-03-21 08:13:19,684 ERROR
com.tst.hadoop.flume.writer.inventory.AccountPersistenceImpl: Error querying