[OVSDB-411] "Too many open files" IOException caused by too many pipe fds accumulated when create ovsdb client Created: 02/May/17 Updated: 07/May/20 Resolved: 07/May/20 |
|
| Status: | Resolved |
| Project: | ovsdb |
| Component/s: | Library |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | guowang | Assignee: | Robert Varga |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: Linux |
||
| Attachments: |
|
||||||||||||
| Issue Links: |
|
||||||||||||
| External issue ID: | 8350 | ||||||||||||
| Description |
|
Everytime when create new connection by method "connectWithSsl", a new event loop will be created(line 149 in file library/impl/src/main/java/org/opendaylight/ovsdb/lib/impl/OvsdbConnectionService.java) but it will never be shutted down; as a result of that, many pipe fds(used by event loop) are accumulated until raise "Too many open files" IOException. To solve the problem described above, suggests that create only one event loop for active client connection, and shutdown it gracefully at OvsdbConnectionService's close() method. p.s. The attachment file is a git-diff file of my solution about this issue. |
| Comments |
| Comment by guowang [ 02/May/17 ] |
|
Attachment diff has been added with description: too many open files exception |
| Comment by OpenDaylight Release [ 03/May/18 ] |
|
Andrew, moving it to you for now. Please decide to who this should be assigned. |
| Comment by Andrew Grimberg [ 03/May/18 ] |
|
You must mean some other Andrew. |
| Comment by Vishal Thapar [ 23/May/18 ] |
|
suneelu Can you check and confirm if this issue is still valid? |
| Comment by Anil Vishnoi [ 01/May/19 ] |
|
suneelu are you still working on this issue ? |
| Comment by Robert Varga [ 05/Dec/19 ] |
|
https://git.opendaylight.org/gerrit/c/ovsdb/+/86161 is fixing this as part of |
| Comment by Robert Varga [ 05/Dec/19 ] |
|
The leak caused here uses anonymous threadpools, whereas |