path: root/tests/basic
diff options
authorKrishnan Parthasarathi <>2015-02-05 15:41:35 +0530
committerVijay Bellur <>2015-02-07 13:25:26 -0800
commitf18a3f30bbeaf3bb067b913082830d7f874555ca (patch)
tree9d283dc48f6158b24acfc4be9176db7b48e50c1c /tests/basic
parenta7f5893c9243c8c563db215352fa7e47f6968e8b (diff)
protocol/client: sequence CHILD_UP, CHILD_DOWN etc notifications
... from all bricks in the volume This patch is important in the context of MT epoll. With MT epoll, notification events from client xlators could reach cluster xlators like afr, dht, ec, stripe etc. in different orders. For e.g, In a distributed replicate volume of 2 bricks, namely Brick1 and Brick2, the following network events are observed by a mount process. - connection to Brick1 is broken. - connection to Brick1 has been restored. - connection to Brick2 is broken. - connection to Brick2 has been restored. Without establishing a total ordering of events, we can't guarantee that cluster xlators like afr, dht perceive them in the same order. While we would expect afr (say) to perceive it as only one of Brick1 and Brick2 going down at any given time, it is possible for the notification of Brick2 going offline to race with the notification of Brick1 coming back online. Change-Id: I78f5a52bfb05593335d0e9ad53ebfff98995593d BUG: 1104462 Signed-off-by: Krishnan Parthasarathi <> Reviewed-on: Tested-by: Gluster Build System <> Reviewed-by: Vijay Bellur <>
Diffstat (limited to 'tests/basic')
0 files changed, 0 insertions, 0 deletions