[
https://issues.apache.org/jira/browse/TIKA-3363?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lewis John McGibbney resolved TIKA-3363.
----------------------------------------
Fix Version/s: (was: 1.27)
Resolution: Won't Fix
> Have tika-docker artifacts start in spawn mode (configurable)
> -------------------------------------------------------------
>
> Key: TIKA-3363
> URL: https://issues.apache.org/jira/browse/TIKA-3363
> Project: Tika
> Issue Type: Improvement
> Components: docker, tika-docker
> Affects Versions: 1.26
> Reporter: Lewis John McGibbney
> Assignee: Lewis John McGibbney
> Priority: Major
>
> I would like to poll tika-docker users as to whether we should turn on by
> default, but make configurable (build and deploy overrides) use of the
> *-spawnChild* flag.
> See
> https://cwiki.apache.org/confluence/display/TIKA/TikaServer#TikaServer-MakingTikaServerRobusttoOOMs,InfiniteLoopsandMemoryLeaks
> for more documentation on this topic.
> Right now it is impossible to configure this in tika-helm unless it is
> configurable from the tika-docker artifact. Thank you
> [~dmeikle] FYI
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
