You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Issue: etcdserver hits a panic in a test case Environment: ubuntu14 docker container with go1.14.2.linux-amd64.tar.gz
Potentially relevant lines in go.mod:
To reproduce: start a single-node etcd cluster, and connect to it with the ETCD v2 client. Then, spawn 100 goroutines, each of which attempts to acquire a lock at /distributed_lock by trying to write its own id to that key. Each goroutine holds the lock for a while (can be simulated with a time.Sleep). Note that I am not using the etcd concurrency package. However, I don't think the issue is within my code because the stacktrace is entirely within etcd's library code. This could be a lesser-hit codepath because it requires writing a request expensive enough to warrant the call to etcdserver.warnOfExpensiveReques, and a type casting between Request and RequestV2.
For certain reasons, it is not very easy for me to upgrade to the v3 client. How possible is it for you guys to take a look at this panic and push a fix?
Issue: etcdserver hits a panic in a test case
Environment: ubuntu14 docker container with go1.14.2.linux-amd64.tar.gz
Potentially relevant lines in go.mod:
To reproduce: start a single-node etcd cluster, and connect to it with the ETCD v2 client. Then, spawn 100 goroutines, each of which attempts to acquire a lock at /distributed_lock by trying to write its own id to that key. Each goroutine holds the lock for a while (can be simulated with a time.Sleep). Note that I am not using the etcd concurrency package. However, I don't think the issue is within my code because the stacktrace is entirely within etcd's library code. This could be a lesser-hit codepath because it requires writing a request expensive enough to warrant the call to etcdserver.warnOfExpensiveReques, and a type casting between Request and RequestV2.
For certain reasons, it is not very easy for me to upgrade to the v3 client. How possible is it for you guys to take a look at this panic and push a fix?
The text was updated successfully, but these errors were encountered: