因此在 etcd v3.1 版本中优化了读请求(PR#6275),使用的方法满足一个简单的策略:每次读操作时记录此时集群的 commit index,当状态机的 apply index 大于或者等于 commit index 时即可返回数据。由于此时状态机已经把读请求所要读的 commit index 对应的日志进行了 apply 操作,符合线性一致读的要求,便可返回此时读...
node3:load and cpu usage is low 2.question-2: "put /data_plane/server_info" have lots of "apply request took too long" error is this the reason why etcd nodes have high cpu usage and load? I don't know why this so simple request had so many error requests. (2). other informati...
"msg":"apply request took too long", "took":"5357.87304ms", "expected-duration":"100ms", "prefix":"read-only range ", "request":"key:\"/registry/pods/\" range_end:\"/registry/pods0\" ", "response":"range_response_count:60077 size:602251227" } 部署和配置调优: K8s events 拆到单...
i get the same lines in the log "etcdserver: apply entries took too long " and "etcdserver: failed to send out heartbeat on time " which mertic you wanted me to check,"etcd_disk_wal_fsync_duration_seconds histogram" ? i am attaching the metrics metrics.32379.txt metrics.22379.txt m...
问题2: "put /data_plane/server_info" 有非常多的 "apply request took too long" 错误,一直打。怀疑这个是etcd的load和cpu很高的原因。 这也是很简单的操作啊: (3).其他信息 etcd cluster 是3个node:etcd cluster is ok. 这个etcd cluster 支持两个 apisix cluster(version: 2.8.0). ...
request ... took too long to execute这类报错也是同理 mvcc: database space exceeded 存储空间不足,参考上面提到的清理和恢复步骤,或者提高存储空间 endpoints问题 尽量不要使用lb 作为 etcd endpoints 配置,etcd client 是 grpc 访问,请使用默认的 全量list ,客户端做负载均衡的方式。详细内容可以参考 grpc 负...
"apply entries took too long" etcd集群接受一个写请求后,每个etcd成员都需要把写请求数据固化到cores/bbolt之中,整个过程不要超过50ms。如果超过100ms,则etcd就会打印此条log进行警告。通常情况下是因为磁盘慢,比如磁盘竞争或者譬如虚拟块磁盘这种烂设备。etcd暴露给Prometheus的metrics指标backendcommitduration_seconds...
true " with result "xxxx" took too long (xxx s) to execute etcdserver: read-only range request "key:\"xxxx" count_only:true " with result "xxxx" took too long (xxxx ms) to execute etcdserver: read-only range request "xxxx" with result "xxxx" took too long (xxx ms) to execute...
1392014:Mar 11 21:56:42 localhost etcd[26312]: request "header:<ID:16363671783383239993 > lease_revoke:<id:1eef70c8a23e4f7a>" with result "error:auth: user name is empty" took too long (1.464µs) to execute ``` 从日志中我们可以看到节点C(3.3+)执行lease_revoke命令时失败了,错误是...
<request_put:<key:\"/registry/masterleases/192.168.217.19\" value_size:70 lease:5373221187761963523 >> failure:<>>" with result "size:18" took too long (122.623655ms) to execute Nov 1 22:55:42 master2 etcd: read-only range request "key:\"/registry/health\" " with result "range_...