curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Cameron McKenzie <mckenzie....@gmail.com>
Subject Re: Trouble with InterProcessMutex.acquire, timeout not respected
Date Wed, 27 Apr 2016 22:11:50 GMT
hey Stefano,
Can you reproduce via a unit test? I imagine that it will be very difficult
for us to reproduce going on the information that you've provided.
cheers
Cam

On Thu, Apr 28, 2016 at 2:32 AM, Stefano Salmaso <
stefano.salmaso@lastminute.com> wrote:

> Forwarding to Curator list...
>
> Hi Jordan,
> I'm using apache curator with zookeeper in order to have a distributed
> lock.
> Our code follow this guide line
> http://curator.apache.org/curator-recipes/shared-reentrant-lock.html
>
> But.. I found that, during network problems (ie using poor mobile
> connection) or with high concurrent request on same path... the tryLock
> timeout is not respected.
> In my test I use 3 seconds... but in those circumstance the timeout is
> higher than expected. (more than 10 seconds.... also 30.. 40)
> I tried with different RetryPolicy and connection timeouts.. but there is
> something wrong.
>
>
> So... I don't know if you can help me.. and if this is the right channel
> for a request like this.... but... I am hopeful!! :-)
>
> Thanks so much
> Stefano.
>
> [image: Bravofly Rumbo Group]
>
> Listed on SIX Swiss Exchange
>
> *Our websites*: lastminute.com | bravofly.com | volagratis.com | rumbo.es
> | jetcost.com | group.lastminute.com
>
> This e-mail may contain confidential and/or privileged information. If you
> are not the intended recipient (or have received this e-mail in error)
> please notify the sender immediately and destroy this e-mail. Any
> unauthorized copying, disclosure or distribution of the material in this
> e-mail is strictly forbidden and could be a crime.
>

Mime
View raw message