Rainer,
thanks for valuable info.
>> Let's see, if this matches your experience: assuming recovery_options=0,
> the request should be retried on other lb member workers (if such exist
> and are OK), unless it's a POST and the POST body is bigger than 8186
> bytes and more than the first 8186 bytes
... adding to previous post:
It also does not retry/fail over, in the following (more or less obvious
cases):
- there was a problem with the client (browser) connection
- we already started to send back parts of the response to the client,
typically the headers (depending on recovery_options;
Dominik Pospisil wrote:
Indeed. It would be OK to return 503, for requests, that already have
been received by the first node, but not returned yet. New requests
That's the case. All errors I am getting are from requests which were allready
in processing by failing node. Why it is OK to return
> Indeed. It would be OK to return 503, for requests, that already have
> been received by the first node, but not returned yet. New requests
That's the case. All errors I am getting are from requests which were allready
in processing by failing node. Why it is OK to return 503 for such requests?
Hi Dominik,
Eventually, after killing 1st node, and after returning couple of "503
Service Temporarily Unavailable" exceptions, mod_jk finally recheck 2nd
node status, reroute requests to 2nd node and resumes correct operation.
Still, I it is not clear to me, why I am getting 503 exceptions.
Hi Rainer,
thanks a lot for prompt response.
> Dominik Pospisil wrote:
> > Hello,
> > I am having following problem with following failover test scenario.
> >
> > Cluster setup:
> > - 1 apache load balancer
> > - 2 nodes with equal LB factor
> > - sticky session turned on
> > - Apache/2.0.52, mod
Hi Dominik,
Dominik Pospisil wrote:
Hello,
I am having following problem with following failover test scenario.
Cluster setup:
- 1 apache load balancer
- 2 nodes with equal LB factor
- sticky session turned on
- Apache/2.0.52, mod_jk/1.2.26
Test scenario:
1. start 1st node
2. start load driver
