[
https://issues.apache.org/jira/browse/CASSANDRA-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13910880#comment-13910880
]
Robert Coli commented on CASSANDRA-6575:
----------------------------------------
FWIW, I +1 this from an operational perspective, especially because there is no
way to inspect a running node to determine if JNA was initialized. My
preference is for (what was merged..) the -D option if you need to override.
> By default, Cassandra should refuse to start if JNA can't be initialized
> properly
> ---------------------------------------------------------------------------------
>
> Key: CASSANDRA-6575
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6575
> Project: Cassandra
> Issue Type: Improvement
> Components: Core
> Reporter: Tupshin Harper
> Assignee: Clément Lardeur
> Priority: Minor
> Labels: lhf
> Fix For: 2.1 beta1
>
> Attachments: trunk-6575-v2.patch, trunk-6575-v3.patch,
> trunk-6575-v4.patch, trunk-6575.patch
>
>
> Failure to have JNA working properly is such a common undetected problem that
> it would be far preferable to have Cassandra refuse to startup unless JNA is
> initialized. In theory, this should be much less of a problem with Cassandra
> 2.1 due to CASSANDRA-5872, but even there, it might fail due to native lib
> problems, or might otherwise be misconfigured. A yaml override, such as
> boot_without_jna would allow the deliberate overriding of this policy.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
