AWS Vertica timeout exceptions


I have a problem on my AWS Vertica (7.1.1-10) cluster site on CentOS 6.
I did a copy cluster from Vertica (7.1.1-10) to AWS Vertica site (CentOS-6 too)… and now I'm getting timeout exceptions only on AWS site (thing that doesn't happening on the source cluster)

I'm connecting to Vertica with DBeaver, DataGrip and Jenkins… and in all programs I'm getting the following error after several minutes:
[HY000][100024] [Vertica][VJDBC](100024) IOException while communicating with server: null. Refer to the inner exception for more detail.


I tried to set some parameters (set them to be same as the source cluster):
# cat /proc/sys/net/ipv4/tcp_keepalive_time
# cat /proc/sys/net/ipv4/tcp_keepalive_intvl
# cat /proc/sys/net/ipv4/tcp_keepalive_probes
But it didn't helped… Still having the problem :(


Do you know what can cause that?
How on one environment I'm not getting this error and in AWS environment I do?


  • Fixed


    We are having DNS Cname on AWS Vertica cluster,

    We increased idle timeout to 5 min from 30 sec



Leave a Comment

BoldItalicStrikethroughOrdered listUnordered list
Align leftAlign centerAlign rightToggle HTML viewToggle full pageToggle lights
Drop image/file

Can't find what you're looking for? Search the Vertica Documentation, Knowledge Base, or Blog for more information.