Home > Storage > ObjectScale and ECS > Product Documentation > Dell ECS: High Availability Design > Update data flow in geo-replicated environment
ECS is architected to allow active/active updating of data from nodes within the associated bucket’s replication group. It can achieve this result by requiring non-object owner sites to synchronously send information about an object update to the primary owner site and wait for acknowledgment before they can send the acknowledgment back to the client. The data related to the updated object is replicated as part of the normal asynchronous chunk replication activities. If the data is not yet replicated to the owning site, and the site receives a read request for the data, the site will request the data from the remote site.
The following figure shows an example of an update request for Object A from a site other than the object owner site.
In this example, the flow of the update operation is as follows:
Note: If Access During Outage is enabled on the bucket or Site 2 is not the object owner, Site 2 contacts the bucket owner first to determine who the current object owner is.
Under normal conditions, the object owner does not change after an update is performed, regardless of which site the update originated from. In this example, the object owner remains Site 1 even after the successful update that originated from Site 2. The only exception is during a temporary site outage if Access During Outage is enabled; for more details, see TSO behavior with Access During Outage enabled.