We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I'm confused by the jepsen.log against etcd 3.5.15, produced by the README instructions:
lein run test --workload lock-set --nemesis pause --time-limit 120
More specifically, Line 893,894,932,955,996:
2024-12-31 07:50:16,609{GMT} INFO [jepsen worker 4] jepsen.util: 4 :invoke :add 51 2024-12-31 07:50:16,611{GMT} INFO [jepsen worker 4] jepsen.etcd.lock: :lease-id 3145927186351753802 :listener #object[io.etcd.jetcd.impl.LeaseImpl$1 0x2f683722 io.etcd.jetcd.impl.LeaseImpl$1@2f683722] 2024-12-31 07:50:19,583{GMT} INFO [jepsen worker 4] jepsen.etcd.lock: :lock {:header {:member-id -2115697703193039960, :revision 107, :raft-term 3}, :key #object[io.etcd.jetcd.ByteSequence 0xaa81ad5 "foo"/2ba8941bafbd8a4a]} 2024-12-31 07:50:21,430{GMT} INFO [jepsen worker 4] jepsen.etcd.lock: :closing {:lease-id 3145927186351753802, :listener #object[io.etcd.jetcd.impl.LeaseImpl$1 0x2f683722 io.etcd.jetcd.impl.LeaseImpl$1@2f683722], :lock-key #object[io.etcd.jetcd.ByteSequence 0xaa81ad5 "foo"/2ba8941bafbd8a4a], :process 4} 2024-12-31 07:50:25,980{GMT} INFO [jepsen worker 4] jepsen.util: 4 :ok :add 51 [:not-found "etcdserver: requested lease not found"]
Where does the "requested lease not found" come from? Are there retries beyond the log?
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I'm confused by the jepsen.log against etcd 3.5.15, produced by the README instructions:
lein run test --workload lock-set --nemesis pause --time-limit 120
More specifically, Line 893,894,932,955,996:
Where does the "requested lease not found" come from? Are there retries beyond the log?
The text was updated successfully, but these errors were encountered: