snilaxan opened a new issue #1149: couchdb sockets leak in half-close state 
(lsof: 'can't identify protocol')
URL: https://github.com/apache/couchdb/issues/1149
 
 
   ## couchdb sockets leak in half-close state (lsof: can't identify protocol)
   openfile counts keep on increasing in CouchDB instance due to `can't 
identify protocol` error in lsof command.
   
   Please find stats related to CouchDB openfile counts in CouchDB installed 
system
    ```
   root@prod-couchdb-c60-master:~# lsof -u couchdb | wc -l
   63770
   ```
   
   ```
   root@couchdb-instance:~# lsof -u couchdb 
   beam.smp  25095 couchdb *101u  sock       0,7        0t0 758313613 can't 
identify protocol
   beam.smp  25095 couchdb *102u  sock       0,7        0t0 758343336 can't 
identify protocol
   beam.smp  25095 couchdb *103u  sock       0,7        0t0 757700976 can't 
identify protocol
   beam.smp  25095 couchdb *104u  sock       0,7        0t0 757942883 can't 
identify protocol
   beam.smp  25095 couchdb *105u  sock       0,7        0t0 782042280 can't 
identify protocol
   ```
   
   ```
   root@couchdb-instance:~# lsof -u couchdb | grep "can't identify protocol" 
|wc -l
   38291
   ```
   
   ## Expected Behavior
   CouchDB should properly handle open files in Linux system.
   
   ## Current Behavior
   It looks like sockets leak in half-close state (lsof: can't identify 
protocol) and the number of openfile counts keeps on increasing on CouchDB 
instance that leads to CouchDB service failures.
   
   
   Please share details for fix this issue or best way for optimizing this 
issue in CouchDB 1.6.1 environment.
   
   ## Your Environment
   <!--- Include as many relevant details about the environment you experienced 
the bug in -->
   * CouchDB version used: 1.6.1
   * Operating System and version (desktop or mobile): Ubuntu 14.04.5 LTS 
   * Erlang R16B03

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

Reply via email to