I am doing a POC for a client who is running Vertica 6.1.2 in AWS
So I have 2 node cluster and I was able to install the software with cluster option with no problems..
When I started to create the database, the will get created on the first node but the 2nd node keep showing down and in the catalog directory under vertica.log I see following message which keeps repeating...
nameless:0x641aeb0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name2014-09-10 16:40:48.001 nameless:0x641aeb0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:49.002 nameless:0x641aeb0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:49.004 Cluster Inviter:0x7fefe800f310 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:49.004 Cluster Inviter:0x7fefe800f310 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:50.001 nameless:0x641aeb0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:51.002 nameless:0x641aeb0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:51.006 Cluster Inviter:0x7fefe800e700 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:51.006 Cluster Inviter:0x7fefe800e700 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:52.002 nameless:0x641aeb0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:53.002 Cluster Inviter:0x7fefe800e700 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:53.002 Cluster Inviter:0x7fefe800e700 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:53.003 nameless:0x641aeb0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:54.000 Timer Service:0x6422050 [Util] <INFO> Task 'AnalyzeRowCount' enabled
2014-09-10 16:40:54.000 Timer Service:0x6422050 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
2014-09-10 16:40:54.000 Timer Service:0x6422050 [Util] <INFO> Task 'LicenseSizeAuditor' enabled
2014-09-10 16:40:54.001 nameless:0x641aeb0 [Catalog] <WARNING> Catalog::getLocalNodeInternal empty node name
Anyone has encountered this or have any clue...
Firewall is off...SELINUX is disabled...
ssh between nodes is all OK.
Vertica 6.1.2 in AWS Cluster getting error when creating database in cluster - getLocalNodeInternal
+1
+2Ensure that all the ports needed for vertica are open. The ports that vertica need are
Vertica
5433 TCP (All connections)
Spread
4803 TCP (Client connections)
4803 UDP (Daemon <-> Daemon)
4804 UDP (Daemon <-> Daemon)
Vertica
5433 TCP (All connections)
Spread
4803 TCP (Client connections)
4803 UDP (Daemon <-> Daemon)
4804 UDP (Daemon <-> Daemon)
+1Hi Eugenia,
I checked the ports and they are available on both nodes..
Node1
tcp 0 0 0.0.0.0:5433 0.0.0.0:* LISTEN tcp 0 0 172.31.27.164:5433 172.31.27.164:57390 ESTABLISHED
tcp 0 0 172.31.27.164:57390 172.31.27.164:5433 ESTABLISHED
tcp 0 0 :::5433 :::* LISTEN
udp 0 0 0.0.0.0:5433 0.0.0.0:*
testclust [root@vertn1 ~]# netstat -an | grep 480
tcp 0 0 0.0.0.0:54804 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:4803 0.0.0.0:* LISTEN
tcp 0 0 172.31.27.164:4803 0.0.0.0:* LISTEN
udp 0 0 127.0.0.1:4803 0.0.0.0:*
udp 0 0 172.31.27.164:4803 0.0.0.0:*
udp 0 0 172.31.31.255:4803 0.0.0.0:*
udp 0 0 127.0.0.1:4804 0.0.0.0:*
udp 0 0 172.31.27.164:4804 0.0.0.0:*
unix 2 [ ACC ] STREAM LISTENING 32701 /tmp/4803
unix 3 [ ] STREAM CONNECTED 35357 /tmp/4803
testclust [root@vertn1 ~]#
Node 2
tcp 0 0 0.0.0.0:5433 0.0.0.0:* LISTEN tcp 0 0 172.31.27.164:5433 172.31.27.164:57390 ESTABLISHED
tcp 0 0 172.31.27.164:57390 172.31.27.164:5433 ESTABLISHED
tcp 0 0 :::5433 :::* LISTEN
udp 0 0 0.0.0.0:5433 0.0.0.0:*
testclust [root@vertn1 ~]# netstat -an | grep 480
tcp 0 0 0.0.0.0:54804 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:4803 0.0.0.0:* LISTEN
tcp 0 0 172.31.27.164:4803 0.0.0.0:* LISTEN
udp 0 0 127.0.0.1:4803 0.0.0.0:*
udp 0 0 172.31.27.164:4803 0.0.0.0:*
udp 0 0 172.31.31.255:4803 0.0.0.0:*
udp 0 0 127.0.0.1:4804 0.0.0.0:*
udp 0 0 172.31.27.164:4804 0.0.0.0:*
unix 2 [ ACC ] STREAM LISTENING 32701 /tmp/4803
unix 3 [ ] STREAM CONNECTED 35357 /tmp/4803
Anything else could be the issue...
Also I have installed with node name and then also with ip address...same issue.
I checked the ports and they are available on both nodes..
Node1
tcp 0 0 0.0.0.0:5433 0.0.0.0:* LISTEN tcp 0 0 172.31.27.164:5433 172.31.27.164:57390 ESTABLISHED
tcp 0 0 172.31.27.164:57390 172.31.27.164:5433 ESTABLISHED
tcp 0 0 :::5433 :::* LISTEN
udp 0 0 0.0.0.0:5433 0.0.0.0:*
testclust [root@vertn1 ~]# netstat -an | grep 480
tcp 0 0 0.0.0.0:54804 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:4803 0.0.0.0:* LISTEN
tcp 0 0 172.31.27.164:4803 0.0.0.0:* LISTEN
udp 0 0 127.0.0.1:4803 0.0.0.0:*
udp 0 0 172.31.27.164:4803 0.0.0.0:*
udp 0 0 172.31.31.255:4803 0.0.0.0:*
udp 0 0 127.0.0.1:4804 0.0.0.0:*
udp 0 0 172.31.27.164:4804 0.0.0.0:*
unix 2 [ ACC ] STREAM LISTENING 32701 /tmp/4803
unix 3 [ ] STREAM CONNECTED 35357 /tmp/4803
testclust [root@vertn1 ~]#
Node 2
tcp 0 0 0.0.0.0:5433 0.0.0.0:* LISTEN tcp 0 0 172.31.27.164:5433 172.31.27.164:57390 ESTABLISHED
tcp 0 0 172.31.27.164:57390 172.31.27.164:5433 ESTABLISHED
tcp 0 0 :::5433 :::* LISTEN
udp 0 0 0.0.0.0:5433 0.0.0.0:*
testclust [root@vertn1 ~]# netstat -an | grep 480
tcp 0 0 0.0.0.0:54804 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:4803 0.0.0.0:* LISTEN
tcp 0 0 172.31.27.164:4803 0.0.0.0:* LISTEN
udp 0 0 127.0.0.1:4803 0.0.0.0:*
udp 0 0 172.31.27.164:4803 0.0.0.0:*
udp 0 0 172.31.31.255:4803 0.0.0.0:*
udp 0 0 127.0.0.1:4804 0.0.0.0:*
udp 0 0 172.31.27.164:4804 0.0.0.0:*
unix 2 [ ACC ] STREAM LISTENING 32701 /tmp/4803
unix 3 [ ] STREAM CONNECTED 35357 /tmp/4803
Anything else could be the issue...
Also I have installed with node name and then also with ip address...same issue.
+1Hi Eugenia,
You were right it was the spread issue. I uninstalled vertica and reinstalled it with -N and -T option and then tested spread. I did not knew about -N and -T has to be used in AWS.
Is -N and -T also required for all later version 7.x and 7.1.x.
Thank you again, I really appreciate your help.
You were right it was the spread issue. I uninstalled vertica and reinstalled it with -N and -T option and then tested spread. I did not knew about -N and -T has to be used in AWS.
Is -N and -T also required for all later version 7.x and 7.1.x.
Thank you again, I really appreciate your help.
+2Yes, the -T is to do message point to point and -N different subnets. That did not change newer versions.
Glad that you resolve your issue.
Eugenia
Glad that you resolve your issue.
Eugenia
Sign up
Already have an account? Login
Welcome to the Rocket Forum!
Please log in or register:
Employee Login | Registration Member Login | RegistrationEnter your E-mail address. We'll send you an e-mail with instructions to reset your password.
77 4th Avenue
Waltham, MA 02451 USA
