[
https://issues.apache.org/jira/browse/HDFS-16042?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17380724#comment-17380724
]
Ahmed Hussein commented on HDFS-16042:
--------------------------------------
*cherry-picking to branch-3.2*
{code:bash}
git cherry-pick -x a2a0283c7be8eac641a256f06731cb6e4bab3b09`
{code}
conflicts due to missing HDFS-14854. "_Create improved decommission monitor
implementation_".
*cherry-picking to branch-2.10*
{code:bash}
git cherry-pick -x a2a0283c7be8eac641a256f06731cb6e4bab3b09`
{code}
conflicts due to missing HDFS-14854. "_Create improved decommission monitor
implementation_".
> DatanodeAdminMonitor scan should be delay based
> -----------------------------------------------
>
> Key: HDFS-16042
> URL: https://issues.apache.org/jira/browse/HDFS-16042
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Reporter: Ahmed Hussein
> Assignee: Ahmed Hussein
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.4.0
>
> Attachments: HDFS-16042-branch-3.2.001.patch,
> HDFS-16042-branch-3.3.001.patch
>
> Time Spent: 1.5h
> Remaining Estimate: 0h
>
> In {{DatanodeAdminManager.activate()}}, the Monitor task is scheduled with a
> fixed rate, ie. the period is from start1 -> start2.
> {code:java}
> executor.scheduleAtFixedRate(monitor, intervalSecs, intervalSecs,
> TimeUnit.SECONDS);
> {code}
> According to Java API docs for {{scheduleAtFixedRate}},
> {quote}If any execution of this task takes longer than its period, then
> subsequent executions may start late, but will not concurrently
> execute.{quote}
> It should be a fixed delay so it's end1 -> start1.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
