[
https://issues.apache.org/jira/browse/HDFS-16502?focusedWorklogId=740385&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-740385
]
ASF GitHub Bot logged work on HDFS-16502:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 12/Mar/22 10:15
Start Date: 12/Mar/22 10:15
Worklog Time Spent: 10m
Work Description: virajjasani opened a new pull request #4064:
URL: https://github.com/apache/hadoop/pull/4064
### Description of PR
Based on the cluster load, it would be helpful to consider tuning block
invalidate limit (dfs.block.invalidate.limit). The only way we can do this
without restarting Namenode as of today is by reconfiguring heartbeat interval
`Math.max(heartbeatInt*20, blockInvalidateLimit)`, this logic is not
straightforward and operators are usually not aware of it (lack of
documentation), also updating heartbeat interval is not desired in all the
cases.
We should provide the ability to alter block invalidation limit without
affecting heartbeat interval on the live cluster to adjust some load at
Datanode level.
We should also take this opportunity to keep (heartbeatInterval * 20)
computation logic in a common method.
### How was this patch tested?
Locally and with UT.
### For code changes:
- [X] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 740385)
Remaining Estimate: 0h
Time Spent: 10m
> Reconfigure Block Invalidate limit
> ----------------------------------
>
> Key: HDFS-16502
> URL: https://issues.apache.org/jira/browse/HDFS-16502
> Project: Hadoop HDFS
> Issue Type: Task
> Reporter: Viraj Jasani
> Assignee: Viraj Jasani
> Priority: Major
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Based on the cluster load, it would be helpful to consider tuning block
> invalidate limit (dfs.block.invalidate.limit). The only way we can do this
> without restarting Namenode as of today is by reconfiguring heartbeat
> interval
> {code:java}
> Math.max(heartbeatInt*20, blockInvalidateLimit){code}
> , this logic is not straightforward and operators are usually not aware of it
> (lack of documentation), also updating heartbeat interval is not desired in
> all the cases.
> We should provide the ability to alter block invalidation limit without
> affecting heartbeat interval on the live cluster to adjust some load at
> Datanode level.
> We should also take this opportunity to keep (heartbeatInterval * 20)
> computation logic in a common method.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
