[
https://issues.apache.org/jira/browse/BEAM-10294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
David Janicek updated BEAM-10294:
---------------------------------
Description:
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.
was:
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.
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.
> 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
> Reporter: David Janicek
> Priority: P2
> Attachments: image-2020-06-22-13-48-08-880.png
>
>
> 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)
