[
https://issues.apache.org/jira/browse/CASSANDRA-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13869572#comment-13869572
]
Brandon Williams commented on CASSANDRA-6575:
---------------------------------------------
We can simply say we didn't start because of a JNA problem, but if they want to
start anyway add 'boot_without_jna: true' to their yaml.
> 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
> Priority: Minor
> Labels: lhf
> Fix For: 2.1
>
>
> 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)
