This is an automated email from the ASF dual-hosted git repository. tballison pushed a commit to branch TIKA-4809-stage-1 in repository https://gitbox.apache.org/repos/asf/tika.git
commit 7ced4544ed183be7989c6fd4c6286af6e6b7930f Author: tallison <[email protected]> AuthorDate: Fri Aug 7 10:35:58 2026 -0400 TIKA-4809: Map CLIENT_UNAVAILABLE_WITHIN_MS to 429 instead of 503 --- .../org/apache/tika/server/core/resource/PipesParsingHelper.java | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/resource/PipesParsingHelper.java b/tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/resource/PipesParsingHelper.java index 89414d2992..7a0660d639 100644 --- a/tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/resource/PipesParsingHelper.java +++ b/tika-server/tika-server-core/src/main/java/org/apache/tika/server/core/resource/PipesParsingHelper.java @@ -282,8 +282,14 @@ public class PipesParsingHelper { EMIT_SUCCESS, EMIT_SUCCESS_PARSE_EXCEPTION, EMIT_SUCCESS_PASSBACK, PARSE_EXCEPTION_NO_EMIT -> Response.Status.OK; - case TIMEOUT, OOM, UNSPECIFIED_CRASH, CLIENT_UNAVAILABLE_WITHIN_MS -> + case TIMEOUT, OOM, UNSPECIFIED_CRASH -> Response.Status.SERVICE_UNAVAILABLE; + // Distinct from the crash statuses above: nothing failed here, the client + // pool was simply at capacity for longer than maxWaitForClientMillis. 429 + // lets monitoring/alerting on HTTP status alone tell "we're at capacity" + // (scale up numClients) apart from "a worker is actually crashing" (503). + case CLIENT_UNAVAILABLE_WITHIN_MS -> + Response.Status.TOO_MANY_REQUESTS; case FETCH_EXCEPTION, EMIT_EXCEPTION, FETCHER_NOT_FOUND, EMITTER_NOT_FOUND, PAYLOAD_LIMIT_EXCEEDED,
