You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tika.apache.org by "Tim Allison (Jira)" <ji...@apache.org> on 2021/02/01 20:10:00 UTC
[jira] [Updated] (TIKA-3289) Allow startup of multiple tika-server
processes from TikaServerCli
[ https://issues.apache.org/jira/browse/TIKA-3289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tim Allison updated TIKA-3289:
------------------------------
Description:
For some use cases, it is useful to start up multiple tika-servers on different ports.
If a user specifies, e.g. {{-p 9995-9998}}, on the commandline, we could start four servers, one on each port.
At the same time, we can refactor some of the forking processes/watch dogs in tika-server.
Obv, this would only work in Tika 2.0's default mode (formerly {{--spawnChild}}), not {{-noFork}} mode.
was:
For some use cases, it is useful to start up multiple tika-servers on different ports.
If a user specifies, e.g. {{-p 9995-9998}}, on the commandline, we could start four servers, one on each port.
At the same time, we can refactor some of the forking processes/watch dogs in tika-server.
> Allow startup of multiple tika-server processes from TikaServerCli
> ------------------------------------------------------------------
>
> Key: TIKA-3289
> URL: https://issues.apache.org/jira/browse/TIKA-3289
> Project: Tika
> Issue Type: Task
> Reporter: Tim Allison
> Assignee: Tim Allison
> Priority: Major
>
> For some use cases, it is useful to start up multiple tika-servers on different ports.
> If a user specifies, e.g. {{-p 9995-9998}}, on the commandline, we could start four servers, one on each port.
> At the same time, we can refactor some of the forking processes/watch dogs in tika-server.
>
> Obv, this would only work in Tika 2.0's default mode (formerly {{--spawnChild}}), not {{-noFork}} mode.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)