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

Lou DeGenaro commented on UIMA-3676:
------------------------------------

       Boot of skeleton DB daemon
       6. Python scripts updated
       7. log4j config updated
       8. WS updated to listen for DB publication and display on Daemons page
       9. Common updated to include DB daemon in list of DUCC daemons
       10. DB Component update to record boot info in DUCC's state directory

> DUCC DB
> -------
>
>                 Key: UIMA-3676
>                 URL: https://issues.apache.org/jira/browse/UIMA-3676
>             Project: UIMA
>          Issue Type: New Feature
>          Components: DUCC
>            Reporter: Lou DeGenaro
>            Assignee: Lou DeGenaro
>
> DUCC currently used flat files of serialized Java objects to store history 
> comprising Jobs, Reservations and Services.  And the WebServer currently 
> caches only the most recent 4096 of each.
> Proposed is to explore the possibility of employing a DB, initially with 
> Apache Derby, to better manage and utilize these potentially large historical 
> data sets.  The DB would be owned by a new DUCC DB daemon and others such as 
> Orchestrater, WebServer and Services Manager would interact with it to store, 
> update and retrieve data.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

Reply via email to