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 503 for such requests?
Why after mod_jk detect failure does not redirect them to second node? I have
recovery_option attribute set to zero.
I am sorry for disturbing you with questins again, but it is really essential
for me to learn how mod_jk failover works in detail.
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 have already been sent to the
backend.
Why doesn't it get retried in this case? Because we only buffer that
many data for retry.
POST bodies can get very big (uploads), so it's not good to buffer
complete POST bodies (could take a lot of memory). AJP tries to stream
packets through the web server to the backend as they arrive. The actual
design simply decides to buffer one ajp packet, which is 8192 bytes
minus ajp head = 8186 bytes.
Does that fit your observations?
Thanks again,
Dominik
Regards,
Rainer
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
