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
