You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@beam.apache.org by "Alexey Romanenko (Jira)" <ji...@apache.org> on 2021/03/23 16:59:00 UTC
[jira] [Updated] (BEAM-10294) Beam metrics are unreadable in Spark
history server
[ https://issues.apache.org/jira/browse/BEAM-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alexey Romanenko updated BEAM-10294:
------------------------------------
Resolution: Fixed
Status: Resolved (was: Resolved)
> 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)