[
https://issues.apache.org/jira/browse/CASSANDRA-11576?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Joshua McKenzie updated CASSANDRA-11576:
----------------------------------------
Resolution: Fixed
Fix Version/s: (was: 3.0.x)
(was: 2.2.x)
(was: 2.1.x)
(was: 3.x)
3.0.8
3.8
2.2.7
2.1.15
Status: Resolved (was: Ready to Commit)
Went ahead and
[commit|https://git-wip-us.apache.org/repos/asf?p=cassandra.git;a=commit;h=a56bc1600bc8b98b9949751873e911ad5b237fbe]
to 2.1 and merged up, as this is a very non-invasive change.
Thanks for the patch!
> Add support for JNA mlockall(2) on POWER
> ----------------------------------------
>
> Key: CASSANDRA-11576
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11576
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Environment: POWER architecture
> Reporter: Rei Odaira
> Assignee: Rei Odaira
> Priority: Minor
> Fix For: 2.1.15, 2.2.7, 3.8, 3.0.8
>
> Attachments: 11576-2.1.txt
>
>
> org.apache.cassandra.utils.CLibrary contains hard-coded C-macro values to be
> passed to system calls through JNA. These values are system-dependent, and as
> far as I investigated, Linux and AIX on the IBM POWER architecture define
> {{MCL_CURRENT}} and {{MCL_FUTURE}} (for mlockall(2)) as different values than
> the current hard-coded values. As a result, mlockall(2) fails on these
> platforms.
> {code}
> WARN 18:51:51 Unknown mlockall error 22
> {code}
> I am going to provide a patch to support JNA mlockall(2) on POWER.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
