You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "László Bodor (Jira)" <ji...@apache.org> on 2026/02/11 09:45:00 UTC

[jira] [Resolved] (HIVE-29444) Log namenode address in testing scenarios

     [ https://issues.apache.org/jira/browse/HIVE-29444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

László Bodor resolved HIVE-29444.
---------------------------------
    Resolution: Fixed

> Log namenode address in testing scenarios
> -----------------------------------------
>
>                 Key: HIVE-29444
>                 URL: https://issues.apache.org/jira/browse/HIVE-29444
>             Project: Hive
>          Issue Type: Improvement
>            Reporter: László Bodor
>            Assignee: László Bodor
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 4.3.0
>
>
> With MiniHS2, which utilizes a MiniDFSCluster it's hard to easily find how to connect to namenode to e.g. run hdfs commands:
> {code}
> 2026-02-06T04:43:54,925  INFO [IPC Server handler 2 on 57080] hdfs.StateChange: BLOCK* registerDatanode: from DatanodeRegistration(127.0.0.1:57082, datanodeUuid=d4abf8c2-0479-4073-a091-9638db8850b9, infoPort=57084, infoSecurePort=0, ipcPort=57085, storageInfo=lv=-57;cid=testClusterID;nsid=1809166803;c=1770381832559) storage d4abf8c2-0479-4073-a091-9638db8850b9
> 2026-02-06T04:43:54,932  INFO [IPC Server handler 2 on 57080] net.NetworkTopology: Adding a new node: /default-rack/127.0.0.1:57082
> 2026-02-06T04:43:54,936  INFO [IPC Server handler 0 on 57080] hdfs.StateChange: BLOCK* registerDatanode: from DatanodeRegistration(127.0.0.1:57087, datanodeUuid=bfaf3b33-5d78-453d-8d0b-c2f6c41d63f8, infoPort=57089, infoSecurePort=0, ipcPort=57090, storageInfo=lv=-57;cid=testClusterID;nsid=1809166803;c=1770381832559) storage bfaf3b33-5d78-453d-8d0b-c2f6c41d63f8
> 2026-02-06T04:43:54,937  INFO [IPC Server handler 0 on 57080] net.NetworkTopology: Adding a new node: /default-rack/127.0.0.1:57087
> 2026-02-06T04:43:55,056  INFO [IPC Server handler 4 on 57080] hdfs.StateChange: BLOCK* registerDatanode: from DatanodeRegistration(127.0.0.1:57091, datanodeUuid=947923d2-1b0c-4f0b-bc7a-d68911987f73, infoPort=57093, infoSecurePort=0, ipcPort=57094, storageInfo=lv=-57;cid=testClusterID;nsid=1809166803;c=1770381832559) storage 947923d2-1b0c-4f0b-bc7a-d68911987f73
> 2026-02-06T04:43:55,064  INFO [IPC Server handler 4 on 57080] net.NetworkTopology: Adding a new node: /default-rack/127.0.0.1:57091
> 2026-02-06T04:43:55,087  INFO [org.apache.hadoop.util.JvmPauseMonitor$Monitor@526b2f3e] util.JvmPauseMonitor: Starting JVM pause monitor
> 2026-02-06T04:43:55,120  WARN [main] common.MetricsLoggerTask: Metrics logging will not be async since the logger is not log4j
> 2026-02-06T04:43:55,153 DEBUG [main] retry.RetryUtils: multipleLinearRandomRetry = MultipleLinearRandomRetry[6x10000ms, 10x60000ms]
> 2026-02-06T04:43:55,318  INFO [IPC Server handler 0 on 57080] hdfs.StateChange: BLOCK* registerDatanode: from DatanodeRegistration(127.0.0.1:57095, datanodeUuid=01cdc654-b96e-4c49-b20a-05851f44b49a, infoPort=57097, infoSecurePort=0, ipcPort=57098, storageInfo=lv=-57;cid=testClusterID;nsid=1809166803;c=1770381832559) storage 01cdc654-b96e-4c49-b20a-05851f44b49a
> 2026-02-06T04:43:55,321  INFO [IPC Server handler 0 on 57080] net.NetworkTopology: Adding a new node: /default-rack/127.0.0.1:57095
> {code}
> A more convenient logging message would be:
> {code}
> 2026-02-06T04:43:55,552  INFO [main] shims.HadoopShimsSecure: Namenode address: localhost/127.0.0.1:57080
> {code}
> this was an in-memory hdfs, so it's not impossible to figure out namenode port from "IPC Server handler 0 on 57080", however, it would be user friendly to just look for "Namenode" in the logs for the same.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)