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
