You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Nicholas DiPiazza (Jira)" <ji...@apache.org> on 2020/12/12 15:32:00 UTC
[jira] [Commented] (TIKA-3247) Make spawnChild default mode for
tika-server in 2.0
[ https://issues.apache.org/jira/browse/TIKA-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17248369#comment-17248369 ]
Nicholas DiPiazza commented on TIKA-3247:
-----------------------------------------
Yeah there is literally never a time I would want the other way around. The spawn child way is the only way I ever use it.
> Make spawnChild default mode for tika-server in 2.0
> ---------------------------------------------------
>
> Key: TIKA-3247
> URL: https://issues.apache.org/jira/browse/TIKA-3247
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Priority: Major
>
> The -spawnChild mode in tika-server forks a child process for the server and will restart on OOM or timeouts. I think this has been baking long enough in the 1.x branch to move to the default mode in 2.x.
> Clients have to be prepared for the server to be in restart mode occasionally. I propose we add a tika-server-client module as an example.
> Users would have a -legacy mode as an option to go back to the less robust old days.
> WDYT? Cc [~ndipiazza_gmail]?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)