[jira] [Updated] (CASSANDRA-18727) JMXUtil.getJmxConnector should retry connection attempts
[ https://issues.apache.org/jira/browse/CASSANDRA-18727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Miklosovic updated CASSANDRA-18727: -- Resolution: Fixed Status: Resolved (was: Open) I think this was delivered in 0.0.16 of in-jvm dtest api hence it might be resolved as fixed. > JMXUtil.getJmxConnector should retry connection attempts > - > > Key: CASSANDRA-18727 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18727 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > We previously added a JMXUtil class that makes it easy for dtests to get a > JMX connection. It ends up that occasionally the JMX server side needs more > time to start up (especially when stopping and restarting instances, which > we’re now doing more frequently, or when stopping and restarting the whole > cluster). In these cases, JMXUtil.getJmxConnector can fail, when it would be > possible to connect if a retry mechanism was added. We should add this > capability to the in-jvm dtest framework. > -- 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-18727) JMXUtil.getJmxConnector should retry connection attempts
[ https://issues.apache.org/jira/browse/CASSANDRA-18727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Joshi updated CASSANDRA-18727: - Reviewers: Alex Petrov, Dinesh Joshi, Jon Meredith (was: Alex Petrov, Jon Meredith) > JMXUtil.getJmxConnector should retry connection attempts > - > > Key: CASSANDRA-18727 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18727 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > We previously added a JMXUtil class that makes it easy for dtests to get a > JMX connection. It ends up that occasionally the JMX server side needs more > time to start up (especially when stopping and restarting instances, which > we’re now doing more frequently, or when stopping and restarting the whole > cluster). In these cases, JMXUtil.getJmxConnector can fail, when it would be > possible to connect if a retry mechanism was added. We should add this > capability to the in-jvm dtest framework. > -- 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-18727) JMXUtil.getJmxConnector should retry connection attempts
[ https://issues.apache.org/jira/browse/CASSANDRA-18727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Doug Rohrer updated CASSANDRA-18727: Change Category: Operability Complexity: Low Hanging Fruit Component/s: Test/dtest/java Reviewers: Alex Petrov, Jon Meredith Assignee: Doug Rohrer Status: Open (was: Triage Needed) > JMXUtil.getJmxConnector should retry connection attempts > - > > Key: CASSANDRA-18727 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18727 > Project: Cassandra > Issue Type: Improvement > Components: Test/dtest/java >Reporter: Doug Rohrer >Assignee: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > We previously added a JMXUtil class that makes it easy for dtests to get a > JMX connection. It ends up that occasionally the JMX server side needs more > time to start up (especially when stopping and restarting instances, which > we’re now doing more frequently, or when stopping and restarting the whole > cluster). In these cases, JMXUtil.getJmxConnector can fail, when it would be > possible to connect if a retry mechanism was added. We should add this > capability to the in-jvm dtest framework. > -- 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-18727) JMXUtil.getJmxConnector should retry connection attempts
[ https://issues.apache.org/jira/browse/CASSANDRA-18727?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated CASSANDRA-18727: --- Labels: pull-request-available (was: ) > JMXUtil.getJmxConnector should retry connection attempts > - > > Key: CASSANDRA-18727 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18727 > Project: Cassandra > Issue Type: Improvement >Reporter: Doug Rohrer >Priority: Normal > Labels: pull-request-available > > We previously added a JMXUtil class that makes it easy for dtests to get a > JMX connection. It ends up that occasionally the JMX server side needs more > time to start up (especially when stopping and restarting instances, which > we’re now doing more frequently, or when stopping and restarting the whole > cluster). In these cases, JMXUtil.getJmxConnector can fail, when it would be > possible to connect if a retry mechanism was added. We should add this > capability to the in-jvm dtest framework. > -- 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
