Dear everybody,
We have problems with the LeaderLatch recipe that I have reflected in
the CURATOR-444 issue. (https://issues.apache.org/jira/browse/CURATOR-444)
One developer was able to systematically reproduce a double leader on
our computers by locking zookeeper with netstat. Our managers are quite
worried. Trying to reproduce the test I have found it very sensible to
timming and I think that may be our timeout configuration is not right. Is
there any configuration requirements for CONNECTION_TIMEOUT_MS and
SESSION_TIMEOUT_MS. Is there any configuration guide?
We are currenty using
15000 ms for connection timeout,
10000 ms for session timeout .
ExponentialRetryPolicy ( base 100ms, max 5000ms)
Anyway, I have created an Issue and added a Pull request that seems to fix
the issue for us. Any feedback about it would be appreciated.
Thanks in advance,
--
Borja Bravo
Software Developer
[email protected]
Forex and CFDs are leveraged products. They may not be a suitable
investment for you as they carry a high degree of risk to your capital and
you can lose more than your initial deposits. Please make sure you
understand all the risks involved. The Darwinex® trademark and the
www.darwinex.com domain are owned by Tradeslide Trading Tech Limited, a
company duly authorised and regulated by the Financial Conduct Authority
(FCA) in the United Kingdom with FRN 586466. Our Company number is 08061368
and our registered office is Acre House, 11-15 William Road, London NW1
3ER, UK
<https://maps.google.com/?q=11-15+William+Road,+London+NW1+3ER,+UK&entry=gmail&source=g>
.
