curator-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jordan Zimmerman <jor...@jordanzimmerman.com>
Subject Re: Using different Retry Policies for the same CuratorFramework instance
Date Mon, 08 Jul 2013 15:36:34 GMT
Can you explain why you want different retry policies for different operations?

> Is it normal to change the underlying CuratorZooKeeperClient's retry policy via the setter
to achieve this?
No. Changing the retry policy changes it for all users in all threads. 

-JZ

On Jul 8, 2013, at 7:57 AM, chao chu <chuchao333@gmail.com> wrote:

> Hi,
> 
> The constructor/factory method to create a CuratorFramework instance need a 'retry policy'.
However, in our case, we may need to use different retry policies for different operations.
> 
> Is it normal to change the underlying CuratorZooKeeperClient's retry policy via the setter
to achieve this?
> 
> Thanks & Regards,
> 
> -- 
> ChuChao


Mime
View raw message