You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "Philip Zampino (Jira)" <ji...@apache.org> on 2024/08/20 16:40:00 UTC

[jira] [Work started] (KNOX-3058) Avoid 404 When Topology Is Being Redeployed

     [ https://issues.apache.org/jira/browse/KNOX-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on KNOX-3058 started by Philip Zampino.
--------------------------------------------
> 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
>
> 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)