[
https://issues.apache.org/jira/browse/CASSANDRASC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17871469#comment-17871469
]
Arjun Ashok commented on CASSANDRASC-140:
-----------------------------------------
+1 for the patch
> Updating traffic shaping options throws IllegalStateException
> -------------------------------------------------------------
>
> Key: CASSANDRASC-140
> URL: https://issues.apache.org/jira/browse/CASSANDRASC-140
> Project: Sidecar for Apache Cassandra
> Issue Type: Bug
> Components: Rest API
> Reporter: Francisco Guerrero
> Assignee: Francisco Guerrero
> Priority: Normal
>
> When updating the traffic shaping options in Sidecar in
> {{org.apache.cassandra.sidecar.server.Server#updateTrafficShapingOptions}},
> we are encountering a bug in vert.x. The problem happens in
> {{io.vertx.core.net.impl.TCPServerBase#updateTrafficShapingOptions}} where
> the {{trafficShapingHandler}} is {{null}} for {{childHandler}}s. When a
> {{null}} {{trafficShapingHandler}} is encountered, the following exception is
> thrown:
> {code:java}
> throw new IllegalStateException("Unable to update traffic shaping options
> because the server was not configured " +
> "to use traffic shaping during startup");
> {code}
> I propose a stopgap measure to fix the issue in Sidecar while we wait for a
> new vert.x release that includes a fix for this issue. Without a fix, we risk
> leaving Sidecar in unknown state after updating the traffic shaping options.
> Because applying the traffic shaping options can succeed or fail before
> encountering the exception. This can potentially leave a cluster of Sidecar
> servers in an inconsistent state across all Sidecars. The only option to
> return to a well-known state is by restarting the Sidecar process across the
> cluster with the updated traffic shaping options applied in the yaml before
> starting the process.
--
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
