Disconnected Satellite
Although a primary server can accept an update even while disconnected from a satellite, avoid this practice, as it can cause administrative complexities. Before attempting to deploy an updated realm definition, check the health of all affiliated servers and correct any network issues.
Consider a situation in which a WAN fault disconnects a satellite cluster from its primary cluster. Nonetheless, an administrator deploys an updated realm definition at a primary. The deployment can proceed (unless some other condition prevents it, such as a No answer from a client).
Meanwhile, if some of the satellites are still operating, they continue to service client requests with information from the outdated realm definition.
When the satellites reconnect to the primaries, the primaries deploy the updated realm definition to the satellites. Because the update is already deployed at other affiliated servers, the primaries do not first test the update against the satellites and their clients. Instead, the primaries deploy the update to the satellites, and the satellites immediately deploy it to their clients, even though the update might cause difficulties for some clients of the satellites.
If you must deploy an updated realm definition in such circumstances, then as the satellites reconnect and deploy the update, it is prudent to carefully monitor the satellites' clients.