Revision 9399dd162848fc7a5153205bfb1f65548d94293b authored by Marek Siarkowicz on 08 March 2024, 10:11:40 UTC, committed by Marek Siarkowicz on 11 March 2024, 19:20:15 UTC
When implementing the fix for progress notifications (https://github.com/etcd-io/etcd/pull/15237) we made a incorrect assumption that that unsynched watches will always get at least one event. Unsynched watches include not only slow watchers, but also newly created watches that requested current or older revision. In case that non of the events match watch filter, those newly created watches might become synched without any event going through. Signed-off-by: Marek Siarkowicz <siarkowicz@google.com>
1 parent 358e3ba
| File | Mode | Size |
|---|---|---|
| leasehttp | ||
| leasepb | ||
| doc.go | -rw-r--r-- | 716 bytes |
| lease_queue.go | -rw-r--r-- | 2.6 KB |
| lease_queue_test.go | -rw-r--r-- | 2.4 KB |
| lessor.go | -rw-r--r-- | 26.2 KB |
| lessor_bench_test.go | -rw-r--r-- | 4.9 KB |
| lessor_test.go | -rw-r--r-- | 19.0 KB |
| metrics.go | -rw-r--r-- | 1.7 KB |
Computing file changes ...
