Because a UG can run under different Users but with the same name and host:port, the UG must be updated to (1) announce its User when it boots up, and (2) check a file's owner_id against the MS-indicated User running the UG that hosts it. If they do NOT match, then assume the remote UG is down: read from an RG, and becoming acting owner on write.
Because a UG can run under different Users but with the same name and host:port, the UG must be updated to (1) announce its User when it boots up, and (2) check a file's owner_id against the MS-indicated User running the UG that hosts it. If they do NOT match, then assume the remote UG is down: read from an RG, and becoming acting owner on write.