[jira] [Updated] (HDFS-16582) Expose aggregate latency of slow node as perceived by the reporting node

2024-01-26 Thread Shilun Fan (Jira)


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

Shilun Fan updated HDFS-16582:
--
Component/s: metrics

> Expose aggregate latency of slow node as perceived by the reporting node
> 
>
> Key: HDFS-16582
> URL: https://issues.apache.org/jira/browse/HDFS-16582
> Project: Hadoop HDFS
>  Issue Type: New Feature
>  Components: metrics
>Affects Versions: 3.4.0, 3.3.5
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.5
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> When any datanode is reported to be slower by another node, we expose the 
> slow node as well as the reporting nodes list for the slow node. However, we 
> don't provide latency numbers of the slownode as reported by the reporting 
> node. Having the latency exposed in the metrics would be really helpful for 
> operators to keep a track of how far behind a given slow node is performing 
> compared to the rest of the nodes in the cluster.
> The operator should be able to gather aggregated latencies of all slow nodes 
> with their reporting nodes in Namenode metrics.



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

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDFS-16582) Expose aggregate latency of slow node as perceived by the reporting node

2024-01-26 Thread Shilun Fan (Jira)


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

Shilun Fan updated HDFS-16582:
--
Affects Version/s: 3.3.5
   3.4.0

> Expose aggregate latency of slow node as perceived by the reporting node
> 
>
> Key: HDFS-16582
> URL: https://issues.apache.org/jira/browse/HDFS-16582
> Project: Hadoop HDFS
>  Issue Type: New Feature
>Affects Versions: 3.4.0, 3.3.5
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Major
>  Labels: pull-request-available
> Fix For: 3.4.0, 3.3.5
>
>  Time Spent: 1.5h
>  Remaining Estimate: 0h
>
> When any datanode is reported to be slower by another node, we expose the 
> slow node as well as the reporting nodes list for the slow node. However, we 
> don't provide latency numbers of the slownode as reported by the reporting 
> node. Having the latency exposed in the metrics would be really helpful for 
> operators to keep a track of how far behind a given slow node is performing 
> compared to the rest of the nodes in the cluster.
> The operator should be able to gather aggregated latencies of all slow nodes 
> with their reporting nodes in Namenode metrics.



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

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDFS-16582) Expose aggregate latency of slow node as perceived by the reporting node

2022-05-17 Thread ASF GitHub Bot (Jira)


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

ASF GitHub Bot updated HDFS-16582:
--
Labels: pull-request-available  (was: )

> Expose aggregate latency of slow node as perceived by the reporting node
> 
>
> Key: HDFS-16582
> URL: https://issues.apache.org/jira/browse/HDFS-16582
> Project: Hadoop HDFS
>  Issue Type: New Feature
>Reporter: Viraj Jasani
>Assignee: Viraj Jasani
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> When any datanode is reported to be slower by another node, we expose the 
> slow node as well as the reporting nodes list for the slow node. However, we 
> don't provide latency numbers of the slownode as reported by the reporting 
> node. Having the latency exposed in the metrics would be really helpful for 
> operators to keep a track of how far behind a given slow node is performing 
> compared to the rest of the nodes in the cluster.
> The operator should be able to gather aggregated latencies of all slow nodes 
> with their reporting nodes in Namenode metrics.



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org