[ 
https://issues.apache.org/jira/browse/HDFS-16502?focusedWorklogId=740692&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-740692
 ]

ASF GitHub Bot logged work on HDFS-16502:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Mar/22 07:40
            Start Date: 14/Mar/22 07:40
    Worklog Time Spent: 10m 
      Work Description: virajjasani edited a comment on pull request #4064:
URL: https://github.com/apache/hadoop/pull/4064#issuecomment-1066468953


   > Do we have a doc somewhere that lists the available configuration keys 
that can be reconfigured? It would be nice for users to understand what can be 
reconfigured.
   
   We don't seem to have a doc as such but operator/admin can use `hdfs 
dfsadmin -reconfig <namenode|datanode> <host:ipc_port> properties` to retrieve 
reconfigurable properties.


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 740692)
    Time Spent: 1.5h  (was: 1h 20m)

> 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
>              Labels: pull-request-available
>          Time Spent: 1.5h
>  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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to