[
https://issues.apache.org/jira/browse/CASSANDRA-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971044#action_12971044
]
Eric Evans commented on CASSANDRA-1820:
---------------------------------------
There are a few reasons why I'm reluctant to apply something like this:
* JMX_PORT is too generic a name for an exported env var. CASSANDRA_JMX_PORT
would be a better name, but changing it will introduce upgrade pain.
* You can already change this sort of thing by specifying an alternate
{{cassandra-env.sh}} using the {{CASSANDRA_CONF}} env var. Too many ways of
accomplishing the same thing can easily result in less usability, not more.
* You could make a similar argument about other configurables,
{{MAX_HEAP_SIZE}} for example. Where do you draw the line? Or should they all
be directly configurable through the environment?
I'm going to close this as Won't Fix, if you disagree with this then feel free
to reopen it and we can take the discussion to a wider group.
Thanks.
> Port 8080 is not always suitable for JMX
> ----------------------------------------
>
> Key: CASSANDRA-1820
> URL: https://issues.apache.org/jira/browse/CASSANDRA-1820
> Project: Cassandra
> Issue Type: Improvement
> Components: Packaging
> Reporter: B. Todd Burruss
> Assignee: B. Todd Burruss
> Priority: Minor
> Fix For: 0.7.0
>
> Attachments: patch.txt
>
> Original Estimate: 0h
> Remaining Estimate: 0h
>
> if JMX_PORT is already set in environment, then cassandra-env.sh will not
> override it.
> patch attached
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
