[ 
https://issues.apache.org/jira/browse/KNOX-3041?focusedWorklogId=1031643&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1031643
 ]

ASF GitHub Bot logged work on KNOX-3041:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 22/Jul/26 10:36
            Start Date: 22/Jul/26 10:36
    Worklog Time Spent: 10m 
      Work Description: github-actions[bot] commented on PR #1317:
URL: https://github.com/apache/knox/pull/1317#issuecomment-5044787609

   ## Test Results
   40 tests   40 ✅  6s ⏱️
    3 suites   0 💤
    3 files     0 ❌
   
   Results for commit a8b63ac8.
   
   
[test-results]:data:application/gzip;base64,H4sIACidYGoC/12Myw6CMBBFf4V07aJabKb+jBmmQzIRqCntivjvFlQe7u45NzmTaqXjUd0qc6rUmCWt4HPEJGEoaAuWI81XrX9wHzPRn3nIs5hNtCjdQXCMIX5NzMNanPch+BFbb+FdbuF9jULfSyqgEBprkACt147IwNUBNOjBc63BWkfMZ8MX9XoDAkTUWv8AAAA=
   




Issue Time Tracking
-------------------

    Worklog Id:     (was: 1031643)
    Time Spent: 20m  (was: 10m)

> Load Balancer backend selection synchronization issue
> -----------------------------------------------------
>
>                 Key: KNOX-3041
>                 URL: https://issues.apache.org/jira/browse/KNOX-3041
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>            Reporter: Istvan Toth
>            Assignee: Tamás Hanicz
>            Priority: Major
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> I was trying to run a benchmark over Knox, with several Http client instances 
> started at the same time on separate threads.
> I found that every single client was directed to the same backend, which was 
> saved in the session, so instead of accessing each backend, every request was 
> directed to a single one.
> While this was a benchmark/load test tool, any non-interactive client can 
> exhibit similar behaviour, defating the point of load balancing.
> Looking at 
> org.apache.knox.gateway.ha.dispatch.ConfigurableHADispatch.executeRequestWrapper(HttpUriRequest,
>  HttpServletRequest, HttpServletResponse) 
> , I think that the sitation could be improved by calling 
> haProvider.makeNextActiveURLAvailable BEFORE the request is executed.
> It would be still racy, but the race window would be dramatically smaller, 
> running some simple local code, which should be on the microsecond scale, 
> instead of performing a full HTTP reqest, which is on on the millisecond 
> scale at best.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to