Wonderful, John, it is working now as per your recommendation.<div>Much appreciated, we can now continue with Vertica install.<div><br><div>You are right, AWS VPC
doesn't allow broadcast traffic. Is there more documentation available about spread ( except for what is on <a href="http://spread.org">spread.org</a> website ) - various configuration examples, how to use spmonitor etc ? </div>
<div> <br><br><div class="gmail_quote">On Sun, Mar 25, 2012 at 7:04 PM, John Schultz <span dir="ltr"><<a href="mailto:jschultz@spreadconcepts.com">jschultz@spreadconcepts.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
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.<br>
<br>
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:<br>
<br>
Spread_Segment <a href="http://127.0.0.1:4803" target="_blank">127.0.0.1:4803</a> {<br>
N010000000010 10.0.0.10 {<br>
10.0.0.10<br>
127.0.0.1<br>
}<br>
}<br>
<br>
Spread_Segment <a href="http://127.0.0.1:4803" target="_blank">127.0.0.1:4803</a> {<br>
N010000000020 10.0.0.20 {<br>
10.0.0.20<br>
127.0.0.1<br>
<div class="im HOEnZb"> }<br>
}<br>
<br>
Cheers!<br>
<br>
-----<br>
John Lane Schultz<br>
Spread Concepts LLC<br>
Phn: <a href="tel:301%20830%208100" value="+13018308100">301 830 8100</a><br>
Cell: <a href="tel:443%20838%202200" value="+14438382200">443 838 2200</a><br>
<br>
</div><div class="HOEnZb"><div class="h5">On Mar 25, 2012, at 5:44 AM, Ranko Mosic wrote:<br>
<br>
Hi John,<br>
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 ).<br>
Vertica installer creates user spread and generates configuration file:<br>
Here is configuration file ( it is identical on host02 ) :<br>
# cat /opt/vertica/config/vspread.conf<br>
Spread_Segment <a href="http://10.0.0.255:4803" target="_blank">10.0.0.255:4803</a> {<br>
N010000000010 10.0.0.10 {<br>
10.0.0.10<br>
127.0.0.1<br>
}<br>
N010000000020 10.0.0.20 {<br>
10.0.0.20<br>
127.0.0.1<br>
}<br>
}<br>
EventLogFile = /dev/null<br>
EventTimeStamp = "[%a %d %b %Y %H:%M:%S]"<br>
DaemonUser = spread<br>
DaemonGroup = verticadba<br>
<br>
<br>
This is spread start command lines from host01 and host02: ( # ps -ef|grep spread )<br>
<br>
spread 2510 1 0 05:30 ? 00:00:00 /opt/vertica/spread/sbin/spread -n N010000000010 -c /opt/vertica/config/vspread.conf<br>
<br>
<br>
spread 2114 1 0 05:30 ? 00:00:00 /opt/vertica/spread/sbin/spread -n N010000000020 -c<br>
/opt/vertica/config/vspread.conf<br>
<br>
<br>
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.<br>
<br>
Netstat shows that ports 480* are used by spread:<br>
<br>
netstat -atupln |grep 480<br>
tcp 0 0 <a href="http://127.0.0.1:4803" target="_blank">127.0.0.1:4803</a> 0.0.0.0:* LISTEN 2510/spread<br>
tcp 0 0 <a href="http://10.0.0.10:4803" target="_blank">10.0.0.10:4803</a> 0.0.0.0:* LISTEN 2510/spread<br>
udp 0 0 <a href="http://127.0.0.1:4803" target="_blank">127.0.0.1:4803</a> 0.0.0.0:* 2510/spread<br>
udp 0 0 <a href="http://10.0.0.10:4803" target="_blank">10.0.0.10:4803</a> 0.0.0.0:* 2510/spread<br>
udp 0 0 <a href="http://10.0.0.255:4803" target="_blank">10.0.0.255:4803</a> 0.0.0.0:* 2510/spread<br>
udp 0 0 <a href="http://127.0.0.1:4804" target="_blank">127.0.0.1:4804</a> 0.0.0.0:* 2510/spread<br>
udp 0 0 <a href="http://10.0.0.10:4804" target="_blank">10.0.0.10:4804</a> 0.0.0.0:* 2510/spread<br>
<br>
<br>
<br>
<br>
<br>
On Sat, Mar 24, 2012 at 4:13 PM, John Schultz <<a href="mailto:jschultz@spreadconcepts.com">jschultz@spreadconcepts.com</a>> wrote:<br>
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.<br>
<br>
Cheers!<br>
<br>
-----<br>
John Lane Schultz<br>
Spread Concepts LLC<br>
Phn: <a href="tel:301%20830%208100" value="+13018308100">301 830 8100</a><br>
Cell: <a href="tel:443%20838%202200" value="+14438382200">443 838 2200</a><br>
<br>
On Mar 24, 2012, at 7:27 AM, Ranko Mosic wrote:<br>
<br>
Hi,<br>
I am trying to get spread nodes to communicate as part of Vertica database install.<br>
/opt/vertica/spread/bin/spuser -r<br>
User> j test<br>
j test<br>
<br>
User><br>
============================<br>
Received REGULAR membership for group test with 1 members, where I am member 0:<br>
<br>
<br>
Same commands issued on host02 also produce identical result ( i.e. nodes do not communicate ).<br>
<br>
What could be the problem here ?<br>
<br>
<br>
<br>
--<br>
Regards,<br>
Ranko Mosic<br>
mobile: <a href="tel:%2B381-60-33-00-464" value="+381603300464">+381-60-33-00-464</a><br>
<br>
_______________________________________________<br>
Spread-users mailing list<br>
<a href="mailto:Spread-users@lists.spread.org">Spread-users@lists.spread.org</a><br>
<a href="http://lists.spread.org/mailman/listinfo/spread-users" target="_blank">http://lists.spread.org/mailman/listinfo/spread-users</a><br>
<br>
<br>
<br>
<br>
--<br>
Regards,<br>
Ranko Mosic<br>
mobile: <a href="tel:%2B381-60-33-00-464" value="+381603300464">+381-60-33-00-464</a><br>
<br>
<br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><font color="#888888" face="arial, sans-serif"><div>Regards,</div><div>Ranko Mosic</div><div>mobile: +381-60-33-00-464 </div></font><br>
</div></div></div>