This repository has been archived by the owner on Oct 7, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 92
zetcd errors with etcd master branch #9
Comments
Running the benchmark, I see a lot of timeouts:
The zk logs show two things zetcd doesn't implement: Renegotiating timeouts; benchmark requests 1s, zk gives 4s:
Limiting max connections to 60 (but zetcd accepts all 100):
If I change the session timeout to 4s in zetcd like zk does, the time-outs all go away. Potential fixes would be to support timeout renegotiation (probably worthwhile) and connection limiting (seems silly) like zk. |
heyitsanthony
pushed a commit
to heyitsanthony/zetcd
that referenced
this issue
Dec 28, 2016
Zookeeper will give timeouts greater than the requested timeout, leading to zetcd connections timing out for respecting the request timeout. Instead, lengthen the timeout if there are too many sessions and the requested timeout is too short. Fixes etcd-io#9
heyitsanthony
pushed a commit
to heyitsanthony/zetcd
that referenced
this issue
Dec 28, 2016
Heavy contention on /zk/cver keys from RMW accesses causes STM to retry too often. Instead, blindly write to cver keys and use the etcd version for the znode stats. Fixes etcd-io#9
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have simple local etcd server + zetcd process and tried to send requests to zetcd but almost all requests error...
Here's how to reproduce
https://github.com/gyuho/zookeeper-tests
https://github.com/gyuho/zookeeper-tests/blob/master/start-server-zetcd.sh
https://github.com/gyuho/zookeeper-tests/blob/master/test-zk.sh
The text was updated successfully, but these errors were encountered: