Olivier:
Sorry about the missing 'i' in your name.
It is clear to me now. Thank you for the detailed
explanation.
Is there a way to force the transfer port to have
a fixed IP address or fixed range of IP addresses?
I assume the data transfer does not use an encrypted
connection (Let me know if this is wrong) so I would
like to have them tunneled through SSL for security
of the data.
Does the CLC actually need to be able to access the
JMX port of the remote controller? It looks like I
do not since the communication will go over the group
protocol.
Thanks,
Neil
--
Neil Aggarwal, (214)986-3533, www.JAMMConsulting.com
FREE! Eliminate junk email and reclaim your inbox.
Visit http://www.spammilter.com for details.
> -----Original Message-----
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf
> Of Olivier Fambon
> Sent: Wednesday, October 25, 2006 1:12 PM
> To: Sequoia general mailing list
> Subject: Re: [Sequoia] Network layout for two geographically
> separate machines
>
> Neil Aggarwal wrote [10/25/2006 07:30 PM]:
> > Oliver:
> >
>
> Niel,
>
> > I am a bit confused.
>
> (you missed an I in my name, but that's ok)
>
> > Is this how things work (It is similar to FTP):
>
> Yes, and actually, that is what it is: a file transfer plague.
>
> > I go t the CLC of a controller (lets say controller 1)
> > and tell it to transfer a dump to controller 2. When
> > I tell controller 1 to do the transfer, I give it the
> > IP address and JMX port of controller 2.
>
> Yes,
>
> > Controller 1 communicates with controller 2 (Using its
> > JMX port) to tell it to receive the dump.
>
> Yes, but no.
>
> Controller 1 communicates with controller 2 using the
> group-communication (although the CLC command uses the jmx 'name' to
> identify the destination controller - and to miss-lead you). And
> controller 1 tells controller 2 to _fetch_ the dump...
>
> > Then, controller 2 binds to a port (choosing one dynamically)
> > and tells controller 1 which port it is listening on.
> > Controller 1 then connects to that port to transfer
> > the data for the dump to controller 2.
>
> ... so it's the other way around: controller 1 binds the port, sends
> port number to controller 2 (via group-comm), which fetches from this
> port. The server is the on that has the data.
>
> > Is this how it works?
>
> You got it almost right.
>
> Hope this helps,
>
> A+O.
>
> _______________________________________________
> Sequoia mailing list
> [email protected]
> https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
