Description of problem: In our cluster, etcd is creating the following lines of logging: 2019-10-30 18:31:50.586126 W | etcdserver: apply entries took too long [234.049436ms for 1 entries] 2019-10-30 18:31:50.594350 W | etcdserver: avoid queries with large range/delete range! 2019-10-30 18:32:28.365469 W | etcdserver: apply entries took too long [162.747778ms for 1 entries] 2019-10-30 18:32:28.365512 W | etcdserver: avoid queries with large range/delete range! 2019-10-30 18:32:54.915433 W | etcdserver: apply entries took too long [128.780285ms for 1 entries] 2019-10-30 18:32:54.915479 W | etcdserver: avoid queries with large range/delete range! 2019-10-30 18:34:53.961394 W | etcdserver: apply entries took too long [152.058509ms for 1 entries] 2019-10-30 18:34:53.961435 W | etcdserver: avoid queries with large range/delete range! 2019-10-30 18:35:05.717219 W | etcdserver: apply entries took too long [154.60006ms for 1 entries] 2019-10-30 18:35:05.717595 W | etcdserver: avoid queries with large range/delete range! However, this log is not actionable for administrators. The log should identify as fully as possible which query/application was too long, so that it can be remedied.
This bug hasn't had any engineering activity in the last ~30 days. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet. As such, we're marking this bug as "LifecycleStale". If you have further information on the current state of the bug, please update it and remove the "LifecycleStale" keyword, otherwise this bug will be automatically closed in 7 days. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.
This is fixed in later version of etcd IE etcd release-3.3[1] [1]https://github.com/etcd-io/etcd/blob/release-3.3/etcdserver/util.go#L157