yangoofy created ZOOKEEPER-4765: ----------------------------------- Summary: high maxlatency & xid out of order Key: ZOOKEEPER-4765 URL: https://issues.apache.org/jira/browse/ZOOKEEPER-4765 Project: ZooKeeper Issue Type: Wish Reporter: yangoofy
1. We use Zookeeper as the registration center for microservices. Zookeeper uses the default configuration. Snapshot600m, with 70w ephemeral nodes. A single Zookeeper server is 56c128g and xmx16g. The number of client connections is 8k, and the number of watches is 400w. During the centralized start and stop time of the client, the maxlatency of the server is as high as 10 seconds. How can I optimize it? 2. Is it necessary for the Zookeeper client to receive a response before verifying the request sent first, otherwise an error will be reported as' xid out of order '? Can we modify it to send requests and responses based on xid matching instead of strong verification order? -- This message was sent by Atlassian Jira (v8.20.10#820010)