On Feb 21, 2008, at 3:56 AM, glassfish_at_javadesktop.org wrote:
> John, you're right, but...
>
> In my original post i wrote about a "cluster environment with a DAS
> on a subnet and two nodes on another subnet, firewalled" exactly for
> these reasons.
>
OK, I missed that post. From a DAS perspective, I think RAM is going
to be the resource to watch. Not much in the way of CPU overhead with
the DAS. As I mentioned, capacity plan as best you can given your
deployment topology and do your best to not starve the DAS of CPU for
when you need to manage the cluster. You can actually shut down the
DAS after the cluster is up-and-running, but then you'll have the
overhead of DAS startup/shutdown to manage the cluster. Probably more
trouble than it is worth. Aim jMeter at the cluster - with your
expected load - while you try to manage the cluster via the DAS, and
that will give you an idea of what it will be like.
> I've tried the solution Node1+DAS / Node2 because for this test i
> "only" have 3 servers:
>
> - 1 Redhat on vmware on a subnet 10.133.x.x (for DAS)
>
> - 2 Redhat on real machines on another subnet 10.138.x.x (for nodes)
>
> I cannot use a vmware machine on 10.138 subnet and clients cannot
> reach 10.133 subnet...
>
> So, i have only 3 chances:
>
> - DAS+ node on a server and node on the other (overhead and no
> recovery plan)
>
> - Three servers on the 10.138 subnet (Money for hardware and
> licenses!!!!!! no good..)
>
> - Find the ports to enable on firewall and use my first plan!
>
> :-)
>
> Thanks again!
> [Message sent by forum member 'shambola' (shambola)]
>
> http://forums.java.net/jive/thread.jspa?messageID=260153
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_glassfish.dev.java.net
> For additional commands, e-mail: users-help_at_glassfish.dev.java.net
>