[
https://issues.apache.org/jira/browse/HDFS-17853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038840#comment-18038840
]
ASF GitHub Bot commented on HDFS-17853:
---------------------------------------
lfxy commented on code in PR #8064:
URL: https://github.com/apache/hadoop/pull/8064#discussion_r2533936267
##########
hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/namenode/FSDirectory.java:
##########
@@ -217,6 +217,8 @@ private static INodeDirectory createRoot(FSNamesystem
namesystem) {
// authorizeWithContext() API or not.
private boolean useAuthorizationWithContextAPI = false;
+ private static final int maxDirItemsLimit = 64 * 100 * 1000;
Review Comment:
The checkstyle suggest MAX_DIR_ITEMS does not conform to naming conventions.
> Support to make dfs.namenode.fs-limits.max-directory-items reconfigurable
> -------------------------------------------------------------------------
>
> Key: HDFS-17853
> URL: https://issues.apache.org/jira/browse/HDFS-17853
> Project: Hadoop HDFS
> Issue Type: Improvement
> Components: namenode
> Affects Versions: 3.5.0
> Reporter: caozhiqiang
> Assignee: caozhiqiang
> Priority: Major
> Labels: pull-request-available
>
> Sometimes, certain directories—such as temporary library directories—contain
> too many subdirectories and files, exceeding the limit defined by the
> {{dfs.namenode.fs-limits.max-directory-items}} configuration. This causes
> many jobs to fail.
> To quickly restore job execution, we need to temporarily adjust this
> configuration. However, since it currently requires to restart NameNode to
> take effect, we need to make it dynamically reconfigurable without restarting
> the NameNode.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
