You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by "Myroslav Opyr (JIRA)" <ji...@apache.org> on 2016/02/01 19:24:39 UTC

[jira] [Commented] (COUCHDB-2912) Hanging _changes in longpoll feed with _doc_ids filter when other document changes

    [ https://issues.apache.org/jira/browse/COUCHDB-2912?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15126715#comment-15126715 ] 

Myroslav Opyr commented on COUCHDB-2912:
----------------------------------------

Is there a chance to get some feedback from any of the devs? Any hint where we can look into the code?

Couch 2.0 is a bit different, since it forces heartbeats on longpoll connections and primary issue (connection hangs) does not reveal themselves. Is there a way to disable hearbeat in lonpoll live sync in Couchdb 2.0?

> Hanging _changes in longpoll feed with _doc_ids filter when other document changes
> ----------------------------------------------------------------------------------
>
>                 Key: COUCHDB-2912
>                 URL: https://issues.apache.org/jira/browse/COUCHDB-2912
>             Project: CouchDB
>          Issue Type: Bug
>          Components: Database Core
>    Affects Versions: 1.6.1
>            Reporter: Myroslav Opyr
>         Attachments: couchdb_clients_requesting_changes.png, couchdb_httpd_request_methods.png, couchdb_httpd_requests.png, couchdb_request_times.png, cpu.png, requirements.txt, test.py
>
>
> Primary issue is:
> # spawn many (70+) longpoll changes requests like:
> /_changes?timeout=26892&style=main_only&include_docs=true&feed=longpoll&filter=_doc_ids&doc_ids=%5B%2253b64bc66e3e4cff9d195c53da691a9b%22%5D&since=95354&limit=25&_nonce=1449572474544
> # change document with id OTHER then 53b64bc66e3e4cff9d195c53da691a9b.
> # all spawned connection never respond (hang forever)
> Secondary is:
> # Clients time-out and close HTTP connection on all spawned longpoll requests
> # CouchDB leaves socket in CLOSE_WAIT state for quite some time consuming available to CouchDB process file descriptors, but eventually (sometimes after quite long time) closes them.
> Tretiary is:
> # Having many sockets in CLOSE_WAIT state (like described above), CouchDB CPU consumption significantly raises overloading the server.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)