[
https://issues.apache.org/jira/browse/HDDS-2136?focusedWorklogId=313623&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-313623
]
ASF GitHub Bot logged work on HDDS-2136:
----------------------------------------
Author: ASF GitHub Bot
Created on: 17/Sep/19 11:05
Start Date: 17/Sep/19 11:05
Worklog Time Spent: 10m
Work Description: adoroszlai commented on pull request #1460: HDDS-2136.
OM block allocation metric not paired with its failures
URL: https://github.com/apache/hadoop/pull/1460
## What changes were proposed in this pull request?
Rename metric member variables for block allocation count and its failures
to have the same prefix to ensure that they appear in the same chart. I think
`BlockAllocations` is both a bit simpler than `BlockAllocateCalls` and more
consistent with other metrics.
https://issues.apache.org/jira/browse/HDDS-2136
## How was this patch tested?
Ran acceptance tests, checked OM Metrics web page.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
Issue Time Tracking
-------------------
Worklog Id: (was: 313623)
Remaining Estimate: 0h
Time Spent: 10m
> OM block allocation metric not paired with its failures
> -------------------------------------------------------
>
> Key: HDDS-2136
> URL: https://issues.apache.org/jira/browse/HDDS-2136
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: Ozone Manager
> Affects Versions: 0.4.1
> Reporter: Doroszlai, Attila
> Assignee: Doroszlai, Attila
> Priority: Minor
> Labels: pull-request-available
> Attachments: allocation_failures.png, allocations.png
>
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Block allocation count and block allocation failure count are shown in
> separate graphs.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
