[
https://issues.apache.org/jira/browse/CASSANALYTICS-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Josh McKenzie updated CASSANALYTICS-145:
----------------------------------------
Fix Version/s: 0.4
Source Control Link:
https://github.com/apache/cassandra-analytics/commit/d8ad57738ed392be2c59ac7589a29832e82d2d5b
Resolution: Fixed
Status: Resolved (was: Ready to Commit)
> Add exception stack walking to port mapping retry logic on analytics
> integration tests
> --------------------------------------------------------------------------------------
>
> Key: CASSANALYTICS-145
> URL: https://issues.apache.org/jira/browse/CASSANALYTICS-145
> Project: Apache Cassandra Analytics
> Issue Type: Task
> Components: Build
> Reporter: Josh McKenzie
> Assignee: Josh McKenzie
> Priority: Normal
> Fix For: 0.4
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> In CASSANALYTICS-138 we got most of the way there, but looks like there's
> still some connection retry failures that can a) have different exception
> messages, and b) be nested in exception call stacks.
> Need to augment that logic a bit to try and keep stamping these port mapping
> failures out.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
