reef-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dongjoon Hyun (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (REEF-1231) replyLookupQueue is not shared, which causes Java-side test failure in Ubuntu
Date Wed, 02 Mar 2016 18:10:18 GMT

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

Dongjoon Hyun commented on REEF-1231:
-------------------------------------

Thank you for filing JIRA issue! 
I'm really interested in this kind of problem. :)
Could you specify your exact test OS version in the field 'Environment'?
I know that the failure repeats many times.

AFAIK, `ulimit -n` is 1024 (default) for all ubuntus: from Travis CI Ubuntu 12.04 to my Ubuntu
15.10.
I'm wondering why my tests on Ubuntu passed in any way and how to make that failure on my
default environment.

> 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)

Mime
View raw message