Hi,
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. java.io.EOFException
I tried to set some parameters (set them to be same as the source cluster):
# cat /proc/sys/net/ipv4/tcp_keepalive_time
120
# cat /proc/sys/net/ipv4/tcp_keepalive_intvl
120
# cat /proc/sys/net/ipv4/tcp_keepalive_probes
45
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?
Thanks
Chen
AWS Vertica timeout exceptions
Moderator: NorbertKrupa
-
- Intermediate
- Posts: 51
- Joined: Wed Sep 09, 2015 9:34 am
- JimKnicely
- Site Admin
- Posts: 1825
- Joined: Sat Jan 21, 2012 4:58 am
- Contact:
Re: AWS Vertica timeout exceptions
Hi,
Is there a firewall running on the cluster you cannot connect? Also, make sure port 5433 is open.
Thanks!
Is there a firewall running on the cluster you cannot connect? Also, make sure port 5433 is open.
Thanks!
Jim Knicely
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
-
- Intermediate
- Posts: 51
- Joined: Wed Sep 09, 2015 9:34 am
Re: AWS Vertica timeout exceptions
Hi Jim,
thank you for your answer.
All the firewalls are closed and the port is open.
I can connect to the cluster and run queries... the problem is that after some time (1-2 min) the connection closed and I need to reconnect.
Thanks
Chen
thank you for your answer.
All the firewalls are closed and the port is open.
I can connect to the cluster and run queries... the problem is that after some time (1-2 min) the connection closed and I need to reconnect.
Thanks
Chen
-
- Intermediate
- Posts: 51
- Joined: Wed Sep 09, 2015 9:34 am
Re: AWS Vertica timeout exceptions
Fixed
We are having DNS Cname on AWS Vertica cluster, we increased idle timeout to 5 min from 30 sec
Thanks
Chen
We are having DNS Cname on AWS Vertica cluster, we increased idle timeout to 5 min from 30 sec
Thanks
Chen
- JimKnicely
- Site Admin
- Posts: 1825
- Joined: Sat Jan 21, 2012 4:58 am
- Contact:
Re: AWS Vertica timeout exceptions
Did that work?
Also, check you ssh setting in the /opt/vertica/config/admin.conf file. There are timeout parameters there too.
Example:
[SSHConfig]
ssh_user =
ssh_ident =
ssh_options = -oConnectTimeout=30 -o TCPKeepAlive=no -o ServerAliveInterval=15 -o ServerAliveCountMax=2 -o StrictHostKeyChecking=no -o BatchMode=yes
Also, check you ssh setting in the /opt/vertica/config/admin.conf file. There are timeout parameters there too.
Example:
[SSHConfig]
ssh_user =
ssh_ident =
ssh_options = -oConnectTimeout=30 -o TCPKeepAlive=no -o ServerAliveInterval=15 -o ServerAliveCountMax=2 -o StrictHostKeyChecking=no -o BatchMode=yes
Jim Knicely
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
-
- Intermediate
- Posts: 51
- Joined: Wed Sep 09, 2015 9:34 am
Re: AWS Vertica timeout exceptions
Increasing the idle timeout fixed my problem
- JimKnicely
- Site Admin
- Posts: 1825
- Joined: Sat Jan 21, 2012 4:58 am
- Contact:
Re: AWS Vertica timeout exceptions
Nice!
Jim Knicely
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.
Note: I work for Vertica. My views, opinions, and thoughts expressed here do not represent those of my employer.