Skip to content

why it took about 8s to time out after publishing fail? Is there any way to shorten the time? #8977

@langkeer

Description

@langkeer

we often meet publishing failure first time, and from the etcd logs, it seems that etcd won't publish again until the timer (duration is 8s) expires. so it will delay the ectd service about 8s. so we want to know:

  1. why don't etcd publish again just after the previous publishing fails?
  2. is there any way to shorten the duration of the timer?
    thanks!

attach part of the etcd logs:
Nov 10 15:06:15 etcd[1627]: peer 75af8d23d13d9b91 became active etcd[1627]: peer 75af8d23d13d9b91 became active
Nov 10 15:06:15 etcd[1627]: established a TCP streaming connection with peer 75af8d23d13d9b91 (stream Message reader) etcd[1627]: established a TCP streaming connection with peer 75af8d23d13d9b91 (stream Message reader)
Nov 10 15:06:15 etcd[1627]: established a TCP streaming connection with peer 75af8d23d13d9b91 (stream MsgApp v2 reader) etcd[1627]: established a TCP streaming connection with peer 75af8d23d13d9b91 (stream MsgApp v2 reader)
Nov 10 15:06:15 etcd[1627]: established a TCP streaming connection with peer 75af8d23d13d9b91 (stream Message writer) etcd[1627]: established a TCP streaming connection with peer 75af8d23d13d9b91 (stream Message writer)
Nov 10 15:06:15 etcd[1627]: established a TCP streaming connection with peer 75af8d23d13d9b91 (stream MsgApp v2 writer) etcd[1627]: established a TCP streaming connection with peer 75af8d23d13d9b91 (stream MsgApp v2 writer)
Nov 10 15:06:15 etcd[1627]: established a TCP streaming connection with peer 5e07cc8337c0395c (stream MsgApp v2 writer) etcd[1627]: established a TCP streaming connection with peer 5e07cc8337c0395c (stream MsgApp v2 writer)
Nov 10 15:06:15 etcd[1627]: established a TCP streaming connection with peer 5e07cc8337c0395c (stream Message writer) etcd[1627]: established a TCP streaming connection with peer 5e07cc8337c0395c (stream Message writer)
Nov 10 15:06:23 etcd[1627]: publish error: etcdserver: request timed out, possibly due to previous leader failure etcd[1627]: publish error: etcdserver: request timed out, possibly due to previous leader failure
Nov 10 15:06:23 etcd[1627]: ready to serve client requests etcd[1627]: published {Name:mn-0 ClientURLs:[http://192.168.1.6:2379]} to cluster d89ecb0dff10fcd4
Nov 10 15:06:23 etcd[1627]: ready to serve client requests
Nov 10 15:06:23 etcd[1627]: published {Name:mn-0 ClientURLs:[http://192.168.1.6:2379]} to cluster d89ecb0dff10fcd4

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions