You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Joshua McKenzie (JIRA)" <ji...@apache.org> on 2014/02/13 19:29:19 UTC
[jira] [Commented] (CASSANDRA-6575) By default, Cassandra should
refuse to start if JNA can't be initialized properly
[ https://issues.apache.org/jira/browse/CASSANDRA-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13900574#comment-13900574 ]
Joshua McKenzie commented on CASSANDRA-6575:
--------------------------------------------
v3 has a refactor using static imports from SystemUtils that is causing dependency errors at runtime. Reverted that portion of the change as functionality should be identical - attaching v4.
Otherwise looks good and tests fine on OSX and linux.
> 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-v3.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)