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 information the etcd cluster have 3 nodes ...
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...
i've set up a 3 node etcd cluster on some raspberry pi 4s using docker. etcd is compiled from source during docker image build using go version 1.15.8. Perhabs because i am using sdcards instead of ssd for storage during testing, i get lots of "request took too long" warnings flood...
If all messages have been applied, don't apply an empty messages list; otherwise appliedi will update to 0 and etcd will panic. Fixes #4278
Rebase the branch If you have a local git environment and meet the criteria below, one option is to rebase the branch and add your Signed-off-by lines in the new commits. Please note that if others have already begun work based upon the commits in this branch, this solution will rewrite...
This pull-request has been approved by: vrutkovs Once this PR has been reviewed and has the lgtm label, please assign elbehery for approval. For more information see the Kubernetes Code Review Process. The full list of commands accepted by this bot can be found here. Needs approval from ...