[
https://issues.apache.org/jira/browse/CASSANALYTICS-179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18099642#comment-18099642
]
Lukasz Antoniak commented on CASSANALYTICS-179:
-----------------------------------------------
CI link:
https://app.circleci.com/pipelines/gh/lukasz-antoniak/cassandra-analytics/329/details?useNewPipelines=true&workflowId=d617d0d1-b2a3-4931-94d7-0d407a89b962#step-108-
!image-2026-07-28-09-57-46-663.png|width=1098,height=617!
> Correct total timeout calculation for getAllNodeSettings
> --------------------------------------------------------
>
> Key: CASSANALYTICS-179
> URL: https://issues.apache.org/jira/browse/CASSANALYTICS-179
> Project: Apache Cassandra Analytics
> Issue Type: Bug
> Components: Writer
> Reporter: Lukasz Antoniak
> Assignee: Lukasz Antoniak
> Priority: Normal
> Attachments: image-2026-07-28-09-57-46-663.png
>
>
> Total timeout waiting for response to all node settings is calculated as:
> {code:java}
> conf.getSidecarRequestMaxRetryDelayMillis() * conf.getSidecarRequestRetries()
> * allNodeSettingFutures.size(); {code}
> The per-request timeout is not taken into account. Most likely sufficient
> timeout is reached due to multiplication by number of "futures". Calculation
> should be corrected to:
> {code:java}
> (maxRetryDelayMillis + requestTimeout) * maxRetries {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
