[
https://issues.apache.org/jira/browse/CASSANDRA-1820?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12971067#action_12971067
]
B. Todd Burruss 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.
for you particular points:
- i don't think changing the name would introduce that much pain. since there
isn't a way to set the JMX_PORT except by using custom scripts i figure most
folks just don't do it
- 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
- where do i think it should stop? i think easy wins like port numbers should
be configurable via environment.
thx
> 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.
