I think this is unrelated, but I want to communicate it: in spawnChild mode, the child _should_ terminate if the parent terminates. If you aren't seeing this behavior and you're on > 1.23, let us know.
Given that the child process _is the server_, it would have to be up to get the request to turn back on. We could add a "last time accessed" end point if that would help... If we had that, you'd probably also want to know what the load was in the last x minutes so that you could decide whether or not to add more servers. Are you putting your tika-servers behind a load-balancer? On Wed, Jul 8, 2020 at 9:55 PM Nicholas DiPiazza < [email protected]> wrote: > Does the tika "spawnChild" option allow for idle tika child processes to be > killed and respawned when needed? > > We fire up about 5 of these things when our major indexing and parsing > begins, but the processes will remain up even after indexing ends. > > Is there a way to tell the child processes to die after a certain amount of > idle time, then spin back up when needed? > > Or is there some "last time accessed" that stores a timestamp of the last > time an API resource was accessed? I could accomplish a reaper daemon that > kills the idle processes that way too. > > -Nicholas >
