[Spread-users] Spread nodes not communicating

John Schultz jschultz at spreadconcepts.com
Sun Mar 25 13:04:47 EDT 2012


My first guesses would be that Amazon doesn't allow broadcast traffic to flow or that the virtual network is not a /24 so .255 is the wrong broadcast address.

If you only ever expect to run a 2 node configuration, then I believe you will get equivalent performance if you put each of the daemons in its own Spread_Segment like this:

Spread_Segment 127.0.0.1:4803 {
  N010000000010    10.0.0.10 {
    10.0.0.10
    127.0.0.1
  }
}

Spread_Segment 127.0.0.1:4803 {
  N010000000020    10.0.0.20 {
    10.0.0.20
    127.0.0.1
  }
} 

Cheers!

-----
John Lane Schultz
Spread Concepts LLC
Phn: 301 830 8100
Cell: 443 838 2200

On Mar 25, 2012, at 5:44 AM, Ranko Mosic wrote:

Hi John, 
I am installing spread ( it is actually automatically installed as part of Vertica database installation procedure ) on two Amazon Web Services Virtual Private Cloud nodes, host01 ( private IP 10.0.0.10 ) and host02 ( 10.0.0.20 ). SELinux is disabled, firewall is shut down ( /etc/init.d/iptables stop ). 
Vertica installer creates user spread and generates configuration file: 
Here is configuration file ( it is identical on host02 ) :
# cat /opt/vertica/config/vspread.conf
Spread_Segment 10.0.0.255:4803 {
  N010000000010    10.0.0.10 {
    10.0.0.10
    127.0.0.1
  }
  N010000000020    10.0.0.20 {
    10.0.0.20
    127.0.0.1
  }
}
EventLogFile = /dev/null
EventTimeStamp = "[%a %d %b %Y %H:%M:%S]"
DaemonUser = spread
DaemonGroup = verticadba


This is spread start command lines from host01 and host02: ( # ps -ef|grep spread )

spread    2510     1  0 05:30 ?        00:00:00 /opt/vertica/spread/sbin/spread -n N010000000010 -c /opt/vertica/config/vspread.conf


spread    2114     1  0 05:30 ?        00:00:00 /opt/vertica/spread/sbin/spread -n N010000000020 -c 
 /opt/vertica/config/vspread.conf


So hostnames are host01, host02, yet somehow Vertica installer puts N010000000010 and N010000000020 as hostnames in configuration file. It also uses same hostnames to start spread. 
 
Netstat shows that ports 480* are used by spread: 

netstat -atupln |grep 480
tcp        0      0 127.0.0.1:4803              0.0.0.0:*                   LISTEN      2510/spread 
tcp        0      0 10.0.0.10:4803              0.0.0.0:*                   LISTEN      2510/spread 
udp        0      0 127.0.0.1:4803              0.0.0.0:*                               2510/spread 
udp        0      0 10.0.0.10:4803              0.0.0.0:*                               2510/spread 
udp        0      0 10.0.0.255:4803             0.0.0.0:*                               2510/spread 
udp        0      0 127.0.0.1:4804              0.0.0.0:*                               2510/spread 
udp        0      0 10.0.0.10:4804              0.0.0.0:*                               2510/spread 





On Sat, Mar 24, 2012 at 4:13 PM, John Schultz <jschultz at spreadconcepts.com> wrote:
Post your configuration file, describe your networking and make sure that any firewalls are open on the port you use along with port+1 and port+2 for UDP traffic.

Cheers!

-----
John Lane Schultz
Spread Concepts LLC
Phn: 301 830 8100
Cell: 443 838 2200

On Mar 24, 2012, at 7:27 AM, Ranko Mosic wrote:

Hi,
I am trying to get spread nodes to communicate as part of Vertica database install.
 /opt/vertica/spread/bin/spuser -r
User> j test
j test

User>
============================
Received REGULAR membership for group test with 1 members, where I am member 0:


Same commands issued on host02 also produce identical result ( i.e. nodes do not communicate ).

What could be the problem here ?



--
Regards,
Ranko Mosic
mobile:   +381-60-33-00-464

_______________________________________________
Spread-users mailing list
Spread-users at lists.spread.org
http://lists.spread.org/mailman/listinfo/spread-users




-- 
Regards,
Ranko Mosic
mobile:   +381-60-33-00-464      


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3805 bytes
Desc: not available
Url : http://lists.spread.org/pipermail/spread-users/attachments/20120325/79a66db1/attachment.bin 


More information about the Spread-users mailing list