[
https://issues.apache.org/jira/browse/TIKA-4523?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tim Allison updated TIKA-4523:
------------------------------
Description:
This is a proposal.
We can dramatically simplify our codebase by removing the forking that we do in
tika-server that we initially added for robustness against OOM and crashing
back in the day.
There are several ways that users can auto-restart.
* systemd or similar
* docker – restart=always
* k8s – similar
Other recs for auto-restart?
Is anyone still relying on this feature and not in a containerized world yet?
was:
We can dramatically simplify our codebase by removing the forking that we do in
tika-server that we initially added for robustness against OOM and crashing
back in the day.
There are several ways that users can auto-restart.
* systemd or similar
* docker – restart=always
* k8s – similar
Other recs for auto-restart?
Is anyone still relying on this feature and not in a containerized world yet?
> Remove forking processes in tika-server for 4.x
> -----------------------------------------------
>
> Key: TIKA-4523
> URL: https://issues.apache.org/jira/browse/TIKA-4523
> Project: Tika
> Issue Type: Sub-task
> Reporter: Tim Allison
> Priority: Major
>
> This is a proposal.
> We can dramatically simplify our codebase by removing the forking that we do
> in tika-server that we initially added for robustness against OOM and
> crashing back in the day.
> There are several ways that users can auto-restart.
> * systemd or similar
> * docker – restart=always
> * k8s – similar
> Other recs for auto-restart?
> Is anyone still relying on this feature and not in a containerized world yet?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
