Ingo Kampe wrote [01/26/2007 11:05 AM]:
Hi all,
I have a setup with iptables activated on cluster nodes. The following ports are
allowed between the nodes:
# 21080: sequoia appia group communication
# 21090: sequoia JMX
# 25322: sequoia JDBC
TCP_SYNC_DEST_ALLOWED="22 21080 21090 25322"
Everything works fine, sequoia see both sides as cluster members and sync data
and so on.
BUT the "transfer dump" command does not work!
The transfer dump command dynamically allocates ports on each file
transfer operation (the point was to have a cheap 'session key').
Is there the possibility to configure a ftp passive mode like behaviour to use
fix source and target tcp ports for transfer dump?
Nope, currently, you can not force the port.
This was filed sometime ago as
https://forge.continuent.org/jira/browse/SEQUOIA-830
If you have several NICs, you can which is to be used via the dumpServer
option of the <Backuper> element in your vdb.xml files, but not the port.
In the meantime, you may consider sharing your dumps via nfs and use
option "nocopy" on the transfer dump command. This will bypass file
transfer, thus the need to care about those ports.
Hope this help,
A+O.
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
