[
https://issues.apache.org/jira/browse/KNOX-3058?focusedWorklogId=931246&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-931246
]
ASF GitHub Bot logged work on KNOX-3058:
----------------------------------------
Author: ASF GitHub Bot
Created on: 21/Aug/24 22:11
Start Date: 21/Aug/24 22:11
Worklog Time Spent: 10m
Work Description: pzampino merged PR #929:
URL: https://github.com/apache/knox/pull/929
Issue Time Tracking
-------------------
Worklog Id: (was: 931246)
Time Spent: 1h 50m (was: 1h 40m)
> Avoid 404 When Topology Is Being Redeployed
> -------------------------------------------
>
> Key: KNOX-3058
> URL: https://issues.apache.org/jira/browse/KNOX-3058
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Philip Zampino
> Assignee: Philip Zampino
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> While a topology is being redeployed, if it is requested, the client receives
> an HTTP 404 response. Most clients will not retry when receiving a 404, so
> the interaction will fail.
> If Knox were to respond with a more retry-friendly response (e.g., HTTP 503),
> then clients could overcome these small windows of unavailability with
> retries.
> The difficult part may be distinguishing topology removal from topology
> inactivity. I think a deleted topology should still result in a 404.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
