Replies: 1 comment
-
It's not possible for only chunk servers. There is an option to route communication with master (metadata) through another interface than i/o communication, but i/o communication includes communication with clients (mounts). If you wanted to use the option that is built-in in MooseFS, then you need to set corresponding IP numbers for the two interfaces in your chunk server machines. For example, if you have 9 chunk servers and 6 of them are connected via another set of interfaces, you can do something like: CS1: first interface: 10.0.1.1, second interface: 10.0.2.1 REMAP_BITS = 29 In this scenario ALL clients (mounts) MUST have access to 10.0.2.0 network, because the remapping will work for both chunk servers and clients. What this does: each time a module (client/chunkserver) asks the master for the address of a chunkserver it needs to talk with (to replicate a chunk, to write/read data to/from a chunk), the master, before sending the address, looks if maybe it needs to be re-mapped. So chunkservers connected to the master via 10.0.1.0/29 IP numbers will be presented to the asking module as a corresponding number from 10.0.2.0/29 class, the first 29 bits of the address will be re-mapped, the last 3 bits (0-7) will be unchanged. So all modules talk to the master on the 10.0.1.0 network, but the six first chunk servers will talk with each other on the 10.0.2.0 network AND all the existing clients will talk with the first six chunk servers on the 10.0.2.0 network. |
Beta Was this translation helpful? Give feedback.
-
Is it possible to have some chunk servers to talk with each other through another interface? Some of them are directly connected on a dedicated interface.
Beta Was this translation helpful? Give feedback.
All reactions