cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Shuler (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-11695) Move JMX connection config to cassandra.yaml
Date Fri, 16 Sep 2016 15:53:21 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15496638#comment-15496638
] 

Michael Shuler commented on CASSANDRA-11695:
--------------------------------------------

That last JMX issue was a low level network bind problem when configurations collided. I haven't
looked at the patch details, but we ought to be able to find potential problems running dev
branch dtest jobs, as well as possibly dtest upgrades along with a custom dtest branch, if
needed. Looks like you ran a unit test and found an issue - we'll just need to do the same
with dtests and find the breakage :)

> Move JMX connection config to cassandra.yaml
> --------------------------------------------
>
>                 Key: CASSANDRA-11695
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-11695
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Configuration
>            Reporter: Sam Tunnicliffe
>            Assignee: Zhongxiang Zheng
>            Priority: Minor
>              Labels: lhf
>             Fix For: 3.x
>
>
> Since CASSANDRA-10091, we always construct the JMX connector server programatically,
so we could move its configuration from cassandra-env to yaml.



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

Mime
View raw message