[
https://issues.apache.org/jira/browse/CASSANDRA-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13884061#comment-13884061
]
Sylvain Lebresne commented on CASSANDRA-6575:
---------------------------------------------
bq. IMO it's better to create a new ticket because the goal was just to
fail-fast if JNA was not available, due to a missing library, a linking
failure, or of an incompatible version.
Well, I'm pretty much -1 on this ticket unless we're able to keep having C*
working out of the box on widely used OS (and OSX is widely used) and this
ticket clearly broke that. Or to put it another, I'll revert this unless we
find what's the problem with OSX and fix it. So I think it's probably ok to
figure out what the problem is on this ticket.
> 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
>
> Attachments: trunk-6575-v2.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)
