You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Tae-Geon Um (JIRA)" <ji...@apache.org> on 2016/03/15 07:55:33 UTC
[jira] [Assigned] (REEF-1231) Too many open files in
NetworkConnectionServiceTest
[ https://issues.apache.org/jira/browse/REEF-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tae-Geon Um reassigned REEF-1231:
---------------------------------
Assignee: Tae-Geon Um
> Too many open files in NetworkConnectionServiceTest
> ---------------------------------------------------
>
> Key: REEF-1231
> URL: https://issues.apache.org/jira/browse/REEF-1231
> Project: REEF
> Issue Type: Bug
> Environment: OS: Ubuntu 12.04 (VirtualBox VM)
> OS: Ubuntu 14.04
> JDK: HotSpot 1.7.0_80
> Reporter: Yunseong Lee
> Assignee: Tae-Geon Um
> Priority: Blocker
> Attachments: reef-0.14.0-rc1-java-ubuntu.log
>
>
> While making {{NameLookupClient}} injectable in REEF-703, and removing the deprecated Constructor in REEF-1124, {{replyLookupQueue}} has become NOT shared between {{NameClient}} and {{NameLookupClient}}. A question regarding this was actually raised by [~MariiaMykhailova] at REEF-703, but the JIRA was resolved without a clear answer.
> This change has not caused any problem in OSX, Windows, and Travis CI's Ubuntu. In other Ubuntu machines, however, {{reef-io}} tests fail due to “too many open files” exception. Tests passed on my Ubuntu VM by increasing the maximum number of open files with “ulimit -n 9999” command.
> But increasing the maximum number is just a workaround; I think a cleaner solution will be to share {{replyLookupQueue}} as we used to. Any thought?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)