Ticket #187 (new enhancement)
Multiple TCP/IP Interfaces are not supported
| Reported by: | Thomas Moschny | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | |
| Component: | uka.karmi | Version: | 1.07g |
| Severity: | normal | Keywords: | |
| Cc: |
Description
Currently it is not possible in a clean and transparent way to direct KaRMI communication over secondary TCP/IP interfaces.
The standard way to setup a cluster with an additional fast interconnect such as Myrinet or Infiniband is to assign IP addresses from a private subnet to the fast interconnect adapters. In most cases InetAddress.getLocalHost() however will return the address of the primary adapter, connected to the (standard) slow Ethernet network. The socket technology only uses this address and thus communicates always using the primary interface.
Solution
Introduce an additional configuration parameter for the socket technology that allows to specify the interface that shall be used by KaRMI, for example a subnet identifier. This way several instances of the socket technology can be used, each of them using a different network. The existing technology selection mechanism could select the appropriate instance for each pair of VMs, totally transparent to the user.
todo since 1.07g.
