You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@knox.apache.org by "ASF subversion and git services (Jira)" <ji...@apache.org> on 2020/12/04 11:21:00 UTC
[jira] [Commented] (KNOX-2478) Cleanup HA Dispatch Implementation
[ https://issues.apache.org/jira/browse/KNOX-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17243948#comment-17243948 ]
ASF subversion and git services commented on KNOX-2478:
-------------------------------------------------------
Commit 9aa87729c0f28293432404d0ec0b1746c7ee099c in knox's branch refs/heads/master from Sandeep Moré
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=9aa8772 ]
KNOX-2478 Logging fix (#390)
> Cleanup HA Dispatch Implementation
> ----------------------------------
>
> Key: KNOX-2478
> URL: https://issues.apache.org/jira/browse/KNOX-2478
> Project: Apache Knox
> Issue Type: Bug
> Components: Server
> Reporter: Sandeep More
> Assignee: Sandeep More
> Priority: Major
> Fix For: 1.6.0
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently the way HA dispatch is set up, it will mark a url failover only when a retry is attempted. This causes two issues
> # When a request fails (say request-1) on the last retry attempt that host (say host-a) is not marked as failover so when a new request (request-2) is made this host (host-a) will be chosen.
> # There could be a use case where the services do not want automatic failover but would like to have new request reach a new host (e.g. by marking retry=0)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)