Browse Source

discovery: remove ResponseHeaderTimeout when discovery

The discovery service doesn't return HTTP header early when watch
starts. This may trigger ResponseHeaderTimeout and cause the watch
request failed.

The fix on discovery service may take some time. Remove the
ResponseHeaderTimeout first so it behaves as before.
Yicheng Qin 10 years ago
parent
commit
1db176151b
1 changed files with 2 additions and 2 deletions
  1. 2 2
      discovery/discovery.go

+ 2 - 2
discovery/discovery.go

@@ -127,8 +127,8 @@ func newDiscovery(durl, dproxyurl string, id types.ID) (*discovery, error) {
 				Timeout:   30 * time.Second,
 				KeepAlive: 30 * time.Second,
 			}).Dial,
-			TLSHandshakeTimeout:   10 * time.Second,
-			ResponseHeaderTimeout: 5 * time.Second,
+			TLSHandshakeTimeout: 10 * time.Second,
+			// TODO: add ResponseHeaderTimeout back when watch on discovery service writes header early
 		},
 		Endpoints: []string{u.String()},
 	}