[
https://issues.apache.org/jira/browse/HADOOP-11954?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14991650#comment-14991650
]
Alan Burlison commented on HADOOP-11954:
----------------------------------------
Whilst returning 0 from NativeIO_getMemlockLimit0 may be OK on Windows as it
doesn't support the mlock() syscall, it doesn't work on Solaris which supports
the syscall but not the RLIMIT_MEMLOCK ulimit. On Solaris we should probably
return MAXINT instead.
> Solaris does not support RLIMIT_MEMLOCK as in Linux
> ---------------------------------------------------
>
> Key: HADOOP-11954
> URL: https://issues.apache.org/jira/browse/HADOOP-11954
> Project: Hadoop Common
> Issue Type: Sub-task
> Affects Versions: 2.2.0, 2.3.0, 2.4.1, 2.5.2, 2.6.0, 2.7.0
> Reporter: Malcolm Kavalsky
> Assignee: Alan Burlison
> Attachments: HADOOP-11954.001.patch
>
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> This affects the JNI call to NativeIO_getMemlockLimit0.
> We can just return 0, as Windows does which also does not support this
> feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
