cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Benedict (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-6575) By default, Cassandra should refuse to start if JNA can't be initialized properly
Date Mon, 24 Mar 2014 08:51:45 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-6575?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13944817#comment-13944817
] 

Benedict commented on CASSANDRA-6575:
-------------------------------------

Note that this dependency is not on a *functioning* JNA, but on the JNA jar itself only, for
Java internal functionality. This dependency is removed anyway once we get CASSANDRA-6694,
so I don't think it is an issue, and if it is we will hopefully fix it shortly regardless.

> 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.2#6252)

Mime
View raw message