You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Lou DeGenaro (JIRA)" <de...@uima.apache.org> on 2017/06/13 12:23:00 UTC

[jira] [Updated] (UIMA-5451) DUCC WebServer (WS) ducc_disk_info runs too often

     [ https://issues.apache.org/jira/browse/UIMA-5451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lou DeGenaro updated UIMA-5451:
-------------------------------
    Description: 
WebServer may be observed having a plethora of threads attempting ducc_disk_info.  Presently this is triggered by each ducc-mon visitor.  

Change the paradigm such that only one WS thread instance of ducc_disk_info is running, and wait 60 minutes between completion of the previous and start of the next invocation of the Python script.  Record the result to WS log.

  was:
WebServer may be observed having a plethora of threads attempting ducc_disk_info.  Presently this is triggered by each ducc-mon visitor.  

Change the paradigm such that only one WS thread instance of ducc_disk_info is running, and wait 5 minutes between completion of the previous and start of the next invocation of the Python script.


> DUCC WebServer (WS) ducc_disk_info runs too often
> -------------------------------------------------
>
>                 Key: UIMA-5451
>                 URL: https://issues.apache.org/jira/browse/UIMA-5451
>             Project: UIMA
>          Issue Type: Improvement
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>             Fix For: 2.1.0-Ducc
>
>
> WebServer may be observed having a plethora of threads attempting ducc_disk_info.  Presently this is triggered by each ducc-mon visitor.  
> Change the paradigm such that only one WS thread instance of ducc_disk_info is running, and wait 60 minutes between completion of the previous and start of the next invocation of the Python script.  Record the result to WS log.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)