You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The http server is designed to delay response with specific number of seconds. Sync_gateway config file does not have timeout value specified. The default timeout value should be 60 seconds but when http server delay more than 60 seconds, the sync_gateway still consider it ok.
Case 1: Delay 70 seconds. Note that the gateway log shows that the post is done 15:55:19 and response is received 70 seconds later at 15:56:29, but SGW did not consider it a timeout
15:55:19.475875 CRUD: Stored doc "doc51" / "1-2b12d23e71d2e9fd08626d60346103dd"
15:55:19.476036 HTTP+: #001: --> 201 (1.4 ms)
15:55:19.477078 Events+: Event queue worker sending event Document change event for doc id: doc51 to: Webhook handler [http://localhost:8081]
15:56:29.481877 Events+: Webhook handler ran for event. Payload posted to URL http://localhost:8081, got status 200 OK
Case 2: Delay 120 seconds. Note that the gateway log shows that the post is done 16:00:02 and response is received 120 seconds later at 16:02:02, but SGW did not consider it a timeout
16:00:02.562170 CRUD: Stored doc "doc51" / "1-a5d8bcf4796760363043c4298e6b5423"
16:00:02.562328 HTTP+: #001: --> 201 (1.4 ms)
16:00:02.562726 Events+: Event queue worker sending event Document change event for doc id: doc51 to: Webhook handler [http://localhost:8081]
16:02:02.568916 Events+: Webhook handler ran for event. Payload posted to URL http://localhost:8081, got status 200 OK
The gateway config file does not have timeout specified and therefore should be default to 60 seconds
The http server is designed to delay response with specific number of seconds. Sync_gateway config file does not have timeout value specified. The default timeout value should be 60 seconds but when http server delay more than 60 seconds, the sync_gateway still consider it ok.
Case 1: Delay 70 seconds. Note that the gateway log shows that the post is done 15:55:19 and response is received 70 seconds later at 15:56:29, but SGW did not consider it a timeout
Case 2: Delay 120 seconds. Note that the gateway log shows that the post is done 16:00:02 and response is received 120 seconds later at 16:02:02, but SGW did not consider it a timeout
The gateway config file does not have timeout specified and therefore should be default to 60 seconds
The text was updated successfully, but these errors were encountered: