I do not. I had read this can cause issues due to NFS file locking. This is why the "slave" systems forward all connections to the "master" node. This way the session DB lives there, and only there. I didn't try the other way, but just avoided it to start with.<br>
<br><br clear="all">Matthew Nicholson<br><a href="mailto:nicholson@eps.harvard.edu">nicholson@eps.harvard.edu</a><br>Harvard University<br>FAS IT Research Computing<br>Dept. Of Earth and Planetary Science<br>
<br><br><div class="gmail_quote">On Wed, May 27, 2009 at 12:05 PM, Prakash Velayutham <span dir="ltr"><<a href="mailto:prakash.velayutham@cchmc.org">prakash.velayutham@cchmc.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div style="">Hi Matt,<div><br></div><div>Thanks for the info. I have a quick question. I am just about getting started to do the same thing.</div><div><br></div><div>Do you have your session DB area shared across the 3 access nodes? If yes, is that via NFS?</div>
<div><br></div><div>Thanks,</div><div>Prakash</div><div><div></div><div class="h5"><div><br><div><div>On May 27, 2009, at 11:58 AM, Matt Nicholson wrote:</div><br><blockquote type="cite">So, this is super-duper late, but, I have/admin a load balanced setup currently:<br>
<br>Basically, we have a BIG cluster, as in 6000+ cores big. We have 3 user accessible access systems, that are access via a DNS round robin. SO, somone connect to xx.yy.zz, and they end up at either xx1,xx2,or xx3.yy.zz.<br>
<br>We wanted to give users NX access to their sessions. /home and anumber of other filesystems are share between all nodes, so this was fairly simple. Since users could end up on any of the 3 systems, I did the following:<br>
<br>xx2 is the "MASTER system", running nx, as a load balancer (just handing clients out randomly really).<br>xx1 and xx3 forward any nx connection to xx2, where they are dealt with. this way if a user connect, runs on xx1, but then suspends, and alter connects and hits xx3, they will get sent back to the "master" system, where it finds their session and reconnects to teh right box.<br>
<br>it works....fairly well. As with NX in general, lots of time has been spend tracking down little errors/issues (someone make a bad edit to their .bashrc, ssh logins work, but NX fails, etc). I'll be sending on issue we have to this list shrotly.<br>
<br>So, there a breif overview of how we have it setup. Feel free to contact me for help/etc.<br><br><br clear="all">Matthew Nicholson<br><br> <br><br><div class="gmail_quote">On Thu, Apr 23, 2009 at 6:12 PM, jhonyl <span dir="ltr"><<a href="mailto:jhonyl@netscape.net" target="_blank">jhonyl@netscape.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> Hi there,<br> <br> Is there some documentation about load balancing in freenx?<br> <br> If not could someone who does it give an overview?<br>
<br> ________________________________________________________________<br> Were you helped on this list with your FreeNX problem?<br> Then please write up the solution in the FreeNX Wiki/FAQ:<br> <br> <a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
<br> Don't forget to check the NX Knowledge Base:<br> <a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br> <br> ________________________________________________________________<br>
FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org" target="_blank">FreeNX-kNX@kde.org</a><br> <a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
________________________________________________________________<br> </blockquote></div><br> ________________________________________________________________<br> Were you helped on this list with your FreeNX problem?<br>
Then please write up the solution in the FreeNX Wiki/FAQ:<br><br><a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
<br> Don't forget to check the NX Knowledge Base:<br> <a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a> <br><br>________________________________________________________________<br>
FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org" target="_blank">FreeNX-kNX@kde.org</a><br> <a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
________________________________________________________________</blockquote></div><br></div></div></div></div><br>________________________________________________________________<br>
Were you helped on this list with your FreeNX problem?<br>
Then please write up the solution in the FreeNX Wiki/FAQ:<br>
<br>
<a href="http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ" target="_blank">http://openfacts2.berlios.de/wikien/index.php/BerliosProject:FreeNX_-_FAQ</a><br>
<br>
Don't forget to check the NX Knowledge Base:<br>
<a href="http://www.nomachine.com/kb/" target="_blank">http://www.nomachine.com/kb/</a><br>
<br>
________________________________________________________________<br>
FreeNX-kNX mailing list --- <a href="mailto:FreeNX-kNX@kde.org">FreeNX-kNX@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/freenx-knx" target="_blank">https://mail.kde.org/mailman/listinfo/freenx-knx</a><br>
________________________________________________________________<br></blockquote></div><br>