[
https://issues.apache.org/jira/browse/CASSANDRA-6518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13937135#comment-13937135
]
Lewis John McGibbney commented on CASSANDRA-6518:
-------------------------------------------------
Hi [~mishail], thanks for looking into this patch. Personally I feel that the
easier it is for users to use MX4j for monitoring the better.
I think we can make the last two lines uncommented by default. This will ensure
that we can pick up cmd line overrides and also edit the address and port
should we wish.
If this is an acceptable compromise then I'll happily update [0] to
accommodate.
Do you require another patch or can you make the changes?
Thanks
[0] https://wiki.apache.org/cassandra/Operations#Monitoring_with_MX4J
> Add in forgotten MX4J variables to cassandra-env.sh
> ---------------------------------------------------
>
> Key: CASSANDRA-6518
> URL: https://issues.apache.org/jira/browse/CASSANDRA-6518
> Project: Cassandra
> Issue Type: Improvement
> Components: Config
> Reporter: Lewis John McGibbney
> Priority: Trivial
> Fix For: 2.1 beta2
>
> Attachments: CASSANDRA-6518.patch
>
>
> It seems that a small patch has been forgotten regarding adding certain MX4J
> configuration variables to cassandra-env.sh. This issue will simply add them
> so folks can easily tweak to suit their setUp.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
