[ 
https://issues.apache.org/jira/browse/TIKA-4844?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18108607#comment-18108607
 ] 

Hudson commented on TIKA-4844:
------------------------------

SUCCESS: Integrated in Jenkins build Tika » tika-main-jdk17 #1583 (See 
[https://ci-builds.apache.org/job/Tika/job/tika-main-jdk17/1583/])
TIKA-4844: scope shared-server restart reports to the process they de… (#3077) 
(github: 
[https://github.com/apache/tika/commit/ab22ec9c9af8a224f3ede600421221d023dcc319])
* (edit) 
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/ServerManager.java
* (edit) 
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/SharedServerManager.java
* (add) 
tika-pipes/tika-pipes-core/src/test/java/org/apache/tika/pipes/core/SharedServerManagerClosedTest.java
* (edit) CHANGES.txt
* (edit) 
tika-pipes/tika-pipes-integration-tests/src/test/java/org/apache/tika/pipes/core/SharedServerModeTest.java
* (edit) 
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/PipesParser.java
* (edit) 
tika-pipes/tika-pipes-core/src/main/java/org/apache/tika/pipes/core/PipesClient.java


> Shared pipes server: stale crash reports trigger spurious restarts of a 
> healthy worker
> --------------------------------------------------------------------------------------
>
>                 Key: TIKA-4844
>                 URL: https://issues.apache.org/jira/browse/TIKA-4844
>             Project: Tika
>          Issue Type: Task
>            Reporter: Tim Allison
>            Priority: Major
>             Fix For: 4.1.0
>
>
> In shared server mode, a client whose in-flight parse was killed by another 
> client's restart files its crash report after that restart completes – 
> ensureRunning holds the lock across the whole fork, so siblings cannot report 
> any earlier. pendingRestart carries no process identity, so the report is 
> applied to the healthy replacement, which is then destroyed and re-forked. 
> One process death produces two restarts and a second round of  destroyed 
> in-flight work. Under sustained concurrent load it sustains itself at one 
> spurious restart per round. Affects 4.0.0 and earlier; shared mode only, 
> which is not the default.



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

Reply via email to