hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Colin Patrick McCabe (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-5049) Add JNI mlock support
Date Fri, 13 Sep 2013 19:23:52 GMT

    [ https://issues.apache.org/jira/browse/HDFS-5049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13766845#comment-13766845

Colin Patrick McCabe commented on HDFS-5049:

With regard to getrlimit: I think it probably makes sense to just add a {{long NativeIO#getMemlockLimit}}
function, and let the JNI layer take care of the details.  Exposing {{getrlimit}} itself,
like we do here, raises some issues: like Chris said, it's not available on Windows.  I also
don't know if the numerical values of the constants are standardized like (RLIMIT_CPU, etc.),
which the current code seems to be assuming.  We should translate {{RLIMIT_INFINITY}} to {{Long.MAX_VALUE}}.

I'll file a follow-up JIRA for this in a moment... or perhaps I should file two follow-up
JIRAs, one for Windows support?
> Add JNI mlock support
> ---------------------
>                 Key: HDFS-5049
>                 URL: https://issues.apache.org/jira/browse/HDFS-5049
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Colin Patrick McCabe
>            Assignee: Andrew Wang
>         Attachments: hdfs-5049-1.patch
> Add support for {{mlock}} and {{munlock}}, for use in caching.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

View raw message