Hide Forgot
I hope it is clear that portmapper will only allow a single GlusterFS (program, version) pair registration on a single machine, preventing us from running multiple bricks on the same server. Unless, every glusterfsd has a different (program, version) pair, but that basically voids the backward compatibility support that was to be brought in using the (program,vers) support. To do what I think we're trying to do, we'll need a GlusterFS specific portmapper that allows connecting to a specific brick on the server. We could do this through a new tool that uses a triple like (program, vers, brick-id/vol-id or whatever else), instead of a tuple like the (program. version).
functionality for bricks to be assigned port numbers at run time and clients resolve it on the fly
PATCH: http://patches.gluster.com/patch/4091 in master (portmap functionality in glusterd)
PATCH: http://patches.gluster.com/patch/4092 in master (rpc-clnt/socket: rpc_clnt_reconfig() API to support overriding of port numbers)
PATCH: http://patches.gluster.com/patch/4093 in master (protocol/client: query portmap and reconnect on new port)
PATCH: http://patches.gluster.com/patch/4231 in master (portmapper program added to glusterfsd mgmt rpc)
PATCH: http://patches.gluster.com/patch/4329 in master (glusterd-pmap: trigger signout by RPC_DISCONNECT event)
REVIEW: http://review.gluster.org/5345 (glusterfsd: is_mgmt_rpc_reconnect should not be `char` but gf_boolean_t) posted (#1) for review on master by Harshavardhana (harsha)
COMMIT: http://review.gluster.org/5345 committed in master by Vijay Bellur (vbellur) ------ commit 333872c8ad93cb9da682d27e89bc2a58cf86aba0 Author: Harshavardhana <harsha> Date: Thu Jul 18 20:52:36 2013 -0700 glusterfsd: is_mgmt_rpc_reconnect should not be `char` but gf_boolean_t Change-Id: I35c4dc040ebb5e926c7f54d823d1c81b1228bd4f BUG: 763046 Signed-off-by: Harshavardhana <harsha> Reviewed-on: http://review.gluster.org/5345 Tested-by: Gluster Build System <jenkins.com> Reviewed-by: Vijay Bellur <vbellur>