[
https://issues.apache.org/jira/browse/HDFS-16902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated HDFS-16902:
--
Component/s: namanode
> Add Namenode status to BPServiceActor metrics and improve logging in
>
[
https://issues.apache.org/jira/browse/HDFS-16902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shilun Fan updated HDFS-16902:
--
Hadoop Flags: Reviewed
Target Version/s: 3.3.6, 3.4.0
Affects Version/s: 3.3.6
[
https://issues.apache.org/jira/browse/HDFS-16902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tao Li updated HDFS-16902:
--
Fix Version/s: 3.2.5
> Add Namenode status to BPServiceActor metrics and improve logging in
> offerservice
>
[
https://issues.apache.org/jira/browse/HDFS-16902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDFS-16902:
--
Labels: pull-request-available (was: )
> Add Namenode status to BPServiceActor metrics and
[
https://issues.apache.org/jira/browse/HDFS-16902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Viraj Jasani updated HDFS-16902:
Description:
Recently came across an k8s environment where randomly some datanode pods are
not