[jira] [Comment Edited] (TIKA-3129) Tika server - track a "last parsed on" timestamp and provide an endpoint to get it

["Nicholas DiPiazza (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TIKA-3129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17180698#comment-17180698 ] 

Nicholas DiPiazza edited comment on TIKA-3129 at 8/19/20, 5:10 PM:
-------------------------------------------------------------------

With respect to "last parsed" offset, I put this feature through it's paces. It works wonderfully.

I think we might benefit by also making this reflect the server's current Out of memory status. so when an OOM has happened, this status should have a flag "inBadStateRestartingShortly" or something until the server is ready to parse again. 


was (Author: ndipiazza_gmail):
With respect to "last parsed" offset, I put this feature through it's paces. It works wonderfully.

I think we might benefit by also making this reflect the server's current Out of memory status. so when an OOM has happened, this status should have a flag "inBadStateRestartingShortly" or something 

> Tika server - track a "last parsed on" timestamp and provide an endpoint to get it
> ----------------------------------------------------------------------------------
>
>                 Key: TIKA-3129
>                 URL: https://issues.apache.org/jira/browse/TIKA-3129
>             Project: Tika
>          Issue Type: Wish
>            Reporter: Nicholas DiPiazza
>            Priority: Major
>
> Need a "last time accessed" that stores a timestamp of the last time an API resource was accessed.
> This is needed so we can set up reaper daemon that kills the idle tika server processes to limit memory consumption, particular on container environments 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)