zookeeper-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mohammad arshad <mohammad.ars...@huawei.com>
Subject How to handle zookeeper data inconsistency
Date Thu, 21 Jan 2016 13:24:48 GMT
Hi All,
I came across a scenario where zookeeper was left in inconsistent state(but that is valid
as per the zookeeper theory) and because of that dependent application's behaved wrongly
The scenario is as follow

1) I have three server Zookeeper cluster, let's say servers are A, B and C. B is the leader
2) In one successful delete operation, a znode znode1 was deleted from A and B but somehow
not deleted from C. The reason for not deleted from C can be either proposal or commit failed.
3) Now for application, which is connected to C, ZooKeeper.exists  returns the znod1 and that
is why application enters into node exists flow which is wrong

shall I check exists from leader only? but even leader can have some node undeleted in the
above scenario
Any guideline to handle the above said valid data inconsistency ??

Any suggestion/help is highly appreciated.

Best Regards
Mohammad Arshad
Huawei Tecnologies India Pvt. Ltd.
Near EPIP Industrial Area, Kundalahalli Village
Whitefield, Bangalore-560066
This e-mail and its attachments contain confidential information from HUAWEI, which
is intended only for the person or entity whose address is listed above. Any use of the
information contained herein in any way (including, but not limited to, total or partial
disclosure, reproduction, or dissemination) by persons other than the intended
recipient(s) is prohibited. If you receive this e-mail in error, please notify the sender
phone or email immediately and delete it!

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message