[
https://issues.apache.org/jira/browse/HDFS-17888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18065148#comment-18065148
]
ASF GitHub Bot commented on HDFS-17888:
---------------------------------------
steveloughran commented on PR #8289:
URL: https://github.com/apache/hadoop/pull/8289#issuecomment-4041124495
ok, merged to trunk (hadoop 3.6).
Can you do a cherrypick pr with branch-3.5 and if yetus is happy, I will
merge without reviewing the code again.
Are the problems you seeing related to using minicluster downstream, or in
hadoop's own tests? If it is downstream, I will try to get into branch-3.5.0
after the branch-3.5 merge
> Fix MiniCluster startup & HttpServer service's conf issues.
> -----------------------------------------------------------
>
> Key: HDFS-17888
> URL: https://issues.apache.org/jira/browse/HDFS-17888
> Project: Hadoop HDFS
> Issue Type: Bug
> Reporter: Zhaobo Huang
> Assignee: Zhaobo Huang
> Priority: Major
> Labels: pull-request-available
> Fix For: 3.6.0
>
>
> Startup MiniCluster
> nohup bin/mapred minicluster -format -nomr > log 2>&1 &
> When using the CLI MiniCluster feature for testing of other functions, the
> following issues were found:
> * Currently, MiniCluster cannot be started due to the absence of the Jupiter
> package.
> * If the HttpServer port is 0, a free port will be randomly assigned, but The
> port on DataNode UI is 0.
> * DataNode HttpServer port usage error. According to NameNode, the port used
> here should be RpcServer, not the port for data transmission.
> + Add logs related to httpServer to view the NameNode httpServer port, making
> it easier for users to find the HttpServer address and view some data.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]