[
https://issues.apache.org/jira/browse/CASSANDRA-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971074#action_12971074
]
Eric Evans commented on CASSANDRA-1820:
---------------------------------------
> my reasoning behind this request is that you guys have put a lot of good work
> into cassandra-env.sh and i hate to duplicate all that into a custom one, just
> to change a port number. this makes my personal upgrade path more painful
> from
> release to release.
I understand, but this is a configuration file. The expectation is that it
will be edited by users to customize for their environments.
If anything, you could make a good argument for 8080 being a bad default, (it
is, and that's probably why most people would need to change it), though it's
also too late in the release cycle for a new default.
> - MAX_HEAP_SIZE was already coded to be configurable since by default it is
> not
> set. this is the very reason i thought that JMX_PORT could also be
> configurable
FWIW, this wasn't the intention. There is a commented entry just above that
expression.
> 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.
