Continuation errors when there are connectivity problems #38

Open
slyphon opened this Issue Jul 25, 2012 · 1 comment

Projects

None yet

1 participant

@slyphon
Contributor
slyphon commented Jul 25, 2012
2012-07-25 13:09:36     _eric   slyphon: so I can recreate the issue with the continuation error
2012-07-25 13:09:44     slyphon oh?
2012-07-25 13:10:21     _eric   20.times { Thread.new { sleep rand; zk.get('/', :watch => true) rescue pp [ $!, $!.backtrace ] } }
2012-07-25 13:10:26     _eric   run that after you've done a
2012-07-25 13:10:34     _eric   kill -STOP <zookeeper pid>

2012-07-25 13:16:18     _eric   it only took a few minutes of doing -STOP -CONT
2012-07-25 13:16:20     _eric   to get it to work
2012-07-25 13:16:30     _eric   but the trick is you have to be calling get with :watch => true or it won't exhibit it
2012-07-25 13:16:35     _eric   without that, it seems to act fine

2012-07-25 15:13:04     slyphon _eric: so, the -STOP -CONT needs to be timed properly?
2012-07-25 15:13:20     slyphon or it can just be -STOP then call with :watch a bunch of times
2012-07-25 15:15:04     _eric   just do kill -STOP
2012-07-25 15:15:06     _eric   do the watches
2012-07-25 15:15:08     _eric   wait until they timeout
2012-07-25 15:15:10     _eric   then do the -CONT
2012-07-25 15:15:22     slyphon kk
@slyphon slyphon was assigned Jul 25, 2012
@slyphon
Contributor
slyphon commented Jul 25, 2012

mention @eric

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment