[
https://issues.apache.org/jira/browse/TIKA-3247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17252013#comment-17252013
]
Tim Allison edited comment on TIKA-3247 at 12/18/20, 9:30 PM:
--------------------------------------------------------------
[~dep4b], I _think_ I fixed your server as a service code to handle this
change, but I know that I didn't add a {{-nofork}} mode. If you have a chance,
can you see if I broke anything. I'm going to commit to main after I get a
clean local build...prob 5-10 min.
was (Author: talli...@mitre.org):
[~dep4b], I _think_ I fixed your server as a service to handle this change, but
I know that I didn't add a {{-nofork}} mode. If you have a chance, can you see
if I broke anything. I'm going to commit to main after I get a clean local
build...prob 5-10 min.
> 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)
