You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@reef.apache.org by "Yunseong Lee (JIRA)" <ji...@apache.org> on 2016/03/02 18:10:18 UTC
[jira] [Updated] (REEF-1231) replyLookupQueue is not shared, which
causes Java-side test failure in Ubuntu
[ https://issues.apache.org/jira/browse/REEF-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Yunseong Lee updated REEF-1231:
-------------------------------
Attachment: reef-0.14.0-rc1-java-ubuntu.log
This is a log from when I run tests with the default ulimit (1024). The first exception is:
{quote}
Caused by: java.net.SocketException: Too many open files
at sun.nio.ch.Net.socket0(Native Method)
at sun.nio.ch.Net.serverSocket(Net.java:445)
at sun.nio.ch.ServerSocketChannelImpl.<init>(ServerSocketChannelImpl.java:88)
at sun.nio.ch.SelectorProviderImpl.openServerSocketChannel(SelectorProviderImpl.java:56)
at io.netty.channel.socket.nio.NioServerSocketChannel.newSocket(NioServerSocketChannel.java:57)
... 36 more
{quote}
> replyLookupQueue is not shared, which causes Java-side test failure in Ubuntu
> ------------------------------------------------------------------------------
>
> Key: REEF-1231
> URL: https://issues.apache.org/jira/browse/REEF-1231
> Project: REEF
> Issue Type: Bug
> Reporter: Yunseong Lee
> 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)