Re: Moving nodes in/out of the cluster on the fly

Scott Ferguson <[email protected]> Thu, 20 Jul 2006 11:05:01 -0700
Newsgroups gmane.text.xml.resin.user
Message-ID <[email protected]>
On Jul 20, 2006, at 7:26 AM, Serge Knystautas wrote:

> There are some new JMX features in the current snapshot that are =20
> supposed to allow you to do this.  I don't see where the =20
> documentation is for how to do this, but if you look at the mbeans, =20=

> you might be able to figure it out.

It would need to be changed on the LoadBalancer.

The stop() operation on the ServerConnectorMXBean will do that in =20
3.0.20.  (The classes are getting changed for 3.0.20.)

I've added a bug track for possibly shutting down a port on the =20
server side.  That one's a bit trickier, though, so it would be in =20
3.1.0.

-- Scott

>
> --=20
> Serge Knystautas
> Lokitech >> software . strategy . design >> http://www.lokitech.com
> p. 301.656.5501
> e. [email protected]
>
> Choate, Bryan (IHG) wrote:
>> All-
>>  Is there a ways to take a node out of the cluster definition, =20
>> such that it=92s still accessible through its own http port but not =20=

>> via the LoadBalanceServlet running on a front end instance?  =20
>> Basically, we have a cluster with multiple front-end instances and =20=

>> multiple back-end instances, and when starting nodes we=92d like to =20=

>> be able to test the functionality on each node ourselves, and then =20=

>> flip a switch to release it to the world, so to speak.  Is there a =20=

>> built-in method of doing this?
>>  Thanks!
>>  **Bryan Choate**
>> InterContinental Hotels Group
>> http://www.ichotelsgroup.com <blocked::http://www.ichotelsgroup.com/>
>> office: 770-604-8179
>>
>
>