hadoop-common-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Raghu Angadi (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HADOOP-3169) LeaseChecker daemon should not be started in DFSClient constructor
Date Wed, 23 Jul 2008 18:31:31 GMT

    [ https://issues.apache.org/jira/browse/HADOOP-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12616211#action_12616211
] 

Raghu Angadi commented on HADOOP-3169:
--------------------------------------

+1 for simple locking  using LeaseChecker object instead of AtomicBoolean and a synchronizedSortedMap.

Also should the LeaseChecker thread be closed when there are no leases pending for a few seconds
or so? The justification is same as the one for delaying creation of the thread.


> LeaseChecker daemon should not be started in DFSClient constructor
> ------------------------------------------------------------------
>
>                 Key: HADOOP-3169
>                 URL: https://issues.apache.org/jira/browse/HADOOP-3169
>             Project: Hadoop Core
>          Issue Type: Improvement
>          Components: dfs
>            Reporter: Tsz Wo (Nicholas), SZE
>            Assignee: Tsz Wo (Nicholas), SZE
>         Attachments: 3169_20080718.patch, 3169_20080721.patch, 3169_20080723b.patch
>
>
> LeaseChecker daemon periodically renew leases with NameNode.  However, if there is no
file creation, LeaseChecker daemon should not be started for saving resources and better performance.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message