Home | About | Sematext search-lucene.com search-hadoop.com
 Search Hadoop and all its subprojects:

Switch to Plain View
Zookeeper, mail # dev - Make zookeeper more test friendly


+
Thawan Kooburat 2013-06-28, 01:39
Copy link to this message
-
Re: Make zookeeper more test friendly
Ted Dunning 2013-06-28, 05:38
+1  this is a very big deal
On Thu, Jun 27, 2013 at 6:39 PM, Thawan Kooburat <[EMAIL PROTECTED]> wrote:

> Many recent issues that I saw internally is due to incorrect handling or
> no sufficient testing on ZooKeeper failure scenario in the custom wrapper
> API or in the applications.
>
> I am thinking that we might be able to expose a few more API calls that
> allow user write unit tests that cover various failure scenarios (similar
> to the TestableZookeer in zookeeper test) . This should also minimize the
> effort on setting the test framework.  Ideally, if we have a mock client
> that don't need a running the server that would be ideal, but I think it is
> too much effort to write and maintain for all the languages. Our internal
> test facility is that we have a dedicated ensemble used by all unit tests.
> This ensure application logic correctness but it is hard to test various
> failure scenarios.
>
> So my current thought is to expose the following functionalities.
>
>   1.  zookeeper_close() that don't actually send close request to the
> server:     This can be used to simulate a client crash without actually
> crashing the test program.
>   2.  Allow client to force triggering CONNECTION_LOSS or SESSSION_EXPIRE
> event:    This will allow the user to test their watchers and callback (and
> possible race condition)
>
> Let me know if you have additional suggestions.
>
>
> --
> Thawan Kooburat
>
+
kishore g 2013-06-28, 08:08
+
Patrick Hunt 2013-07-01, 23:59
+
Jordan Zimmerman 2013-07-06, 15:40
+
Jordan Zimmerman 2013-07-16, 17:22