[jira] [Updated] (CASSANDRA-11695) Move JMX connection config to cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-11695: -- Status: Triage Needed (was: Awaiting Feedback) > 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: Local/Config >Reporter: Sam Tunnicliffe >Assignee: Stefan Miklosovic >Priority: Low > Labels: lhf > Fix For: 5.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 (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11695) Move JMX connection config to cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-11695: -- Change Category: Operability Complexity: Normal (was: Low Hanging Fruit) Status: Open (was: Triage Needed) > 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: Local/Config >Reporter: Sam Tunnicliffe >Assignee: Stefan Miklosovic >Priority: Low > Labels: lhf > Fix For: 5.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 (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11695) Move JMX connection config to cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-11695: -- Fix Version/s: 5.x (was: 3.11.x) > 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: Local/Config >Reporter: Sam Tunnicliffe >Assignee: Stefan Miklosovic >Priority: Low > Labels: lhf > Fix For: 5.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 (v8.20.10#820010) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11695) Move JMX connection config to cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jeremy Hanna updated CASSANDRA-11695: - Complexity: Low Hanging Fruit > 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: Local/Config >Reporter: Sam Tunnicliffe >Assignee: Zhongxiang Zheng >Priority: Low > Labels: lhf > Fix For: 3.11.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 (v7.6.3#76005) - To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org
[jira] [Updated] (CASSANDRA-11695) Move JMX connection config to cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-11695: Status: Awaiting Feedback (was: Open) > 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)
[jira] [Updated] (CASSANDRA-11695) Move JMX connection config to cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sam Tunnicliffe updated CASSANDRA-11695: Assignee: Zhongxiang Zheng Status: Open (was: Patch Available) > 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)
[jira] [Updated] (CASSANDRA-11695) Move JMX connection config to cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Joshua McKenzie updated CASSANDRA-11695: Reviewer: Sam Tunnicliffe > 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 >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)
[jira] [Updated] (CASSANDRA-11695) Move JMX connection config to cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Zhongxiang Zheng updated CASSANDRA-11695: - Status: Patch Available (was: Open) > 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 >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)
[jira] [Updated] (CASSANDRA-11695) Move JMX connection config to cassandra.yaml
[ https://issues.apache.org/jira/browse/CASSANDRA-11695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylvain Lebresne updated CASSANDRA-11695: - Labels: lhf (was: ) > 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 >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)
