xingsuo-zbz opened a new issue, #1248:
URL: https://github.com/apache/curator/issues/1248

   zookeeper version : 3.7.3
   server conf:
   ```
   tickTime=2000
   initLimit=10
   syncLimit=5
   minSessionTimeout=7200000
   maxSessionTimeout=86400000
   ```
   
   curator client conf:
   
   ```
   CuratorFrameworkFactory.builder()
       .connectString(zkQuorum)
       .sessionTimeoutMs(86400000)
       .connectionTimeoutMs(15000)
       .simulatedSessionExpirationPercent(100)
       .retryPolicy(new ExponentialBackoffRetry(5000, 24))
       .namespace("xxx")
       .aclProvider(aclProvider);
   ```
   
   There are 3 zookeeper servers, kill 2 of them, simulate a long-term 
unavailability failure of zookeeper.
   
   The cursor client enters SUSPEND state after the leader is unavailable, and 
is expected to enter LOST state after 1 day, but in reality it will enter LOST 
state after about 8 minutes.
   
   Related logs:
   `2025-02-21 19:03:33,443 [Curator-ConnectionStateManager-0] WARN  
org.apache.flink.shaded.curator5.org.apache.curator.framework.state.ConnectionStateManager
  - Session timeout has elapsed while SUSPENDED. Injecting a session 
expiration. Elapsed ms: 500654. Adjusted session timeout ms: 500654`


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@curator.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to