cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorkild Stray (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (CASSANDRA-10275) Allow LOCAL_JMX to be easily overridden
Date Sun, 06 Sep 2015 19:48:45 GMT

     [ https://issues.apache.org/jira/browse/CASSANDRA-10275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thorkild Stray  updated CASSANDRA-10275:
----------------------------------------
    Attachment: cassandra-2.1.9-10275.txt

Patch against 2.1.9, current stable.

> Allow LOCAL_JMX to be easily overridden
> ---------------------------------------
>
>                 Key: CASSANDRA-10275
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-10275
>             Project: Cassandra
>          Issue Type: Bug
>         Environment: Debian
>            Reporter: Thorkild Stray 
>            Priority: Trivial
>             Fix For: 2.1.x
>
>         Attachments: cassandra-2.1.9-10275.txt
>
>
> After tightening up JMX security in 2.1.4 by making cassandra by default only accept
JMX connections from the same host, the option "LOCAL_JMX" was added to cassandra-env.sh to
override this. 
> But, the option was added in such a way that there is no way to override it (on debian)
through the /etc/default/cassandra file like other options (such as MAX_HEAP_SIZE etc).
> Since cassandra-env.sh contains a lot of logic, patching it means having to maintain
your patches when upgrading, making automation more work. The attached patch makes it possible
to override it externally like other options, and keeping the local configuration separate
from cassandra-env.sh.
> (Shell-code-change tries to mimic the existing pattern in cassandra-env.sh)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message