[ https://issues.apache.org/jira/browse/HDFS-12519?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16198319#comment-16198319 ]
Nandakumar commented on HDFS-12519: ----------------------------------- [~linyiqun], The reason for having {{leaseMonitorThread.interrupt()}} is because we support custom timeout in {{acquire(T resource, long timeout)}}, custom timeout value can be set less than default timeout. In this case we need to re-calculate the sleep time in {{LeaseMonitor}}, because new lease might have less {{remainingTime}} than the one we calculate previously. > Ozone: Add a Lease Manager to SCM > --------------------------------- > > Key: HDFS-12519 > URL: https://issues.apache.org/jira/browse/HDFS-12519 > Project: Hadoop HDFS > Issue Type: Sub-task > Components: ozone > Reporter: Anu Engineer > Assignee: Nandakumar > Labels: OzonePostMerge > Attachments: HDFS-12519-HDFS-7240.000.patch, > HDFS-12519-HDFS-7240.001.patch, HDFS-12519-HDFS-7240.002.patch > > > Many objects, including Containers and pipelines can time out during creating > process. We need a way to track these timeouts. This lease Manager allows SCM > to hold a lease on these objects and helps SCM timeout waiting for creating > of these objects. -- This message was sent by Atlassian JIRA (v6.4.14#64029) --------------------------------------------------------------------- To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org