jepsen-io / jepsen-io/etcd

How to read the history?

Open
#3 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Clojure
Stars
23
Forks
10
PR merge metrics
No merged PRs in 30d

Description

I'm confused by the [jepsen.log](https://github.com/user-attachments/files/18280447/jepsen.log) against etcd 3.5.15, produced by the README instructions:
```shell
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?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the README command `lein run test --workload lock-set --nemesis pause --time-limit 120` and inspect the attached jepsen.log around lines 893, 894, 932, 955, and 996. Trace the logged lease and lock events to explain where `requested lease not found` originates and whether retries appear elsewhere in the log; done means documenting that history clearly.

Written by the indexing model from the issue text.

Assessment

Tech stack
clojure
Domain
distributed-systems, testing-qa
Issue type
Documentation
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.