[ https://issues.apache.org/jira/browse/YARN-4205?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rohith Sharma K S updated YARN-4205: ------------------------------------ Attachment: 0002-YARN-4205.patch As discussed with [~jianhe], thought of using AbstractMonitoring service to monitor applications. The difference from previous patch is # AbstractMonitorService : added register API to pass an time. # Extend the abstract monitoring service and modified such way that monitor individual object with its own expiry interval. For this, added getExpiryInterval method with default implementation to return one expiry interval. If an object has its own expiry interval then it can be extended and return it. #Test : modified test with right assertions. > Add a service for monitoring application life time out > ------------------------------------------------------ > > Key: YARN-4205 > URL: https://issues.apache.org/jira/browse/YARN-4205 > Project: Hadoop YARN > Issue Type: Sub-task > Components: scheduler > Reporter: nijel > Assignee: Rohith Sharma K S > Attachments: 0001-YARN-4205.patch, 0002-YARN-4205.patch, > YARN-4205_01.patch, YARN-4205_02.patch, YARN-4205_03.patch > > > This JIRA intend to provide a lifetime monitor service. > The service will monitor the applications where the life time is configured. > If the application is running beyond the lifetime, it will be killed. > The lifetime will be considered from the submit time. > The thread monitoring interval is configurable. -- This message was sent by Atlassian JIRA (v6.3.4#6332) --------------------------------------------------------------------- To unsubscribe, e-mail: yarn-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: yarn-issues-h...@hadoop.apache.org