[
https://issues.apache.org/jira/browse/BEAM-10294?focusedWorklogId=464033&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-464033
]
ASF GitHub Bot logged work on BEAM-10294:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Jul/20 07:55
Start Date: 29/Jul/20 07:55
Worklog Time Spent: 10m
Work Description: aromanenko-dev commented on pull request #12063:
URL: https://github.com/apache/beam/pull/12063#issuecomment-664983381
----------------------------------------------------------------
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:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 464033)
Time Spent: 4h 20m (was: 4h 10m)
> Beam metrics are unreadable in Spark history server
> ---------------------------------------------------
>
> Key: BEAM-10294
> URL: https://issues.apache.org/jira/browse/BEAM-10294
> Project: Beam
> Issue Type: Bug
> Components: runner-spark
> Affects Versions: 2.13.0
> Reporter: David Janicek
> Assignee: David Janicek
> Priority: P2
> Fix For: 2.24.0
>
> Attachments: image-2020-06-22-13-48-08-880.png
>
> Time Spent: 4h 20m
> Remaining Estimate: 0h
>
> Beam metrics shown in Spark history server are not readable. They're rendered
> as JSON which is created from protobuffer defined in *beam_job_api.proto*
> where metric's value is defined as bytes.
> !image-2020-06-22-13-48-08-880.png!
> Similar issue was already addressed and fixed in BEAM-6062 but was broken by
> BEAM-4552.
> Solution could be using *SparkMetricsContainerStepMap* instead of
> *MetricsContainerStepMap* inside *MetricsContainerStepMapAccumulator* as in
> BEAM-6062.
>
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
