what i mean is : the step-1's IO from node1 was received by the OSDs
before the blacklist barrier,
however, still under progress after the blacklist barrier, which might
overwrite the data by node2 and
corrupt our data.
How do we avoid this situation?
On 2017年03月07日 07:47, Jason Dillaman wrote:
On Mon, Mar 6, 2017 at 9:08 AM, peng.hse <peng.hse@xxxxxxxxxxxx> wrote:
3. assuming the step-1 outstanding IO and step-2 IO targeted the same area
of the fs metadata
on the rbd devices. step-2 successfully persist the data and reply to
client.
then, the following laggy IO from step-1 might override and corrupt what
we have written in step-2.
so, how do we prevent this kind of corruption happening?
... but in step (2) you successfully blacklisted the client on node1
(i.e. it is not allowed to talk to the OSDs). Therefore, node1 cannot
overwrite any data written by node2.
--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
