On Wed, Jun 13, 2012 at 10:40 AM, Gregory Farnum <[email protected]> wrote: > 2) Client fencing. See http://tracker.newdream.net/issues/2531. There > is an existing "blacklist" functionality in the OSDs/OSDMap, where you > can specify an "entity_addr_t" (consisting of an IP, a port, and a > nonce — so essentially unique per-process) which is not allowed to > communicate with the cluster any longer. The problem with this is that
Does that work even after a TCP connection close & re-establish, where the client now has a new source port address? (Perhaps the port is 0 for clients?) -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
