Fu Wei
> A quick question, did you reproduce the issue on the latest code of main branch or did you just reproduce it on the code before the fix? Hi @ahrtr...
Yes. Let me try to reproduce it in my local. Update it later.
> Report: [1717749910517706368.tar.gz](https://github.com/user-attachments/files/15734869/1717749910517706368.tar.gz) For this one, the tombstone of `key6` would be deleted by the following compact request **compaction:**. Not sure when the watcher setups watch request. If it setups...
> I managed to reproduce it without multi TXN, just a delete request. This extends the impact to Kubernetes. > Again the common thing is that etcd misses a watch...
> don't understand the statement. Distributed system needs to uphold it's guarantees even if a node is down. Events on WAL used for replay should match what users observes. For...
Thanks @ahrtr for the quick comment. > The existing [CompactorModeRevision](https://github.com/etcd-io/etcd/blob/0d89fa73362f2dbce5ba843e3ac10b16c20d7ab9/server/embed/config.go#L141) can also meet your requirement. We just need to set the same value as the revisionThreshold in your case. The...
Thanks for the review @serathius @ahrtr The painpoint (at least to me) is that the bustable traffic is unpredictable and there is no watchable alerm API (if I understand correctly)...
> What kind of burst you are talking about? Are you expecting data size you double in 5 minutes? The burst is about too many PUT requests to kube-apiserver. I...