Details
-
Bug
-
Resolution: Fixed
-
Major
-
2.5.1, 2.5.0, 2.5.2, 3.0, 3.0.1, 3.0.2, 3.0.3, 3.1.0, 3.1.1, 4.0.0
-
Security Level: Public
-
None
Description
Especially `stale=false` request can block the responses quite a while, when the updater is running. If during that time the client disconnects, the socket isn't released immediately, but only when the updater is finished.
This issue is about releasing the socket even before the indexing is finished in case the client hung up.
Attachments
Issue Links
- relates to
-
MB-25184 Queries continue streaming rows even after TCP connection timeout
- Closed
For Gerrit Dashboard: MB-16737 | ||||||
---|---|---|---|---|---|---|
# | Subject | Branch | Project | Status | CR | V |
56745,1 | MB-16737: Release sockets if client closes connection | master | couchdb | Status: ABANDONED | +1 | -1 |
64651,3 | MB-16737 Set default timeout late | master | couchdb | Status: MERGED | +2 | +1 |
64652,1 | MB-16737 Make it possible to close a socket early | master | couchdb | Status: ABANDONED | 0 | -1 |
64653,3 | MB-16737 Release sockets if internal client closes connection | master | couchdb | Status: ABANDONED | 0 | -1 |
64654,4 | MB-16737 Abort request when connection_timeout is given | master | couchdb | Status: ABANDONED | 0 | -1 |
65426,1 | MB-16737 Release sockets if internal client closes connection | master | couchdb | Status: ABANDONED | 0 | -1 |
89944,4 | MB-16737: [couch_index_merger] Perform socket cleanup ... | unstable | couchdb | Status: MERGED | +2 | +1 |