[
https://issues.apache.org/jira/browse/BEAM-6846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16795594#comment-16795594
]
Kishan Kumar edited comment on BEAM-6846 at 3/19/19 3:37 AM:
-------------------------------------------------------------
[~kenn] , The Performance Issue is coming While Doing GroupBy and Co-GroupBy
Steps Using KV<String,TableRow>. We have Chosen 2.7.0 Due to Availability of
Numeric Support and LTS. Where we can get Some Support from Apache Beam Team.
Note: But when we use Custom Class then it's Working Fine As Expected.
We are Also Planning to move on 2.11.0 Version as Suggested By Google But that
not how we can do it in Production because of Everytime while Upgrading the
Version we again neet to do the Regression Testing and Functional Testing So it
does not Break Anything. Which Takes a Lot of Time.
was (Author: kishank):
[~kenn] , The Performance Issue is coming While Doing GroupBy and Co-GroupBy
Steps Using KV<String,TableRow>. We have Chosen 2.7.0 Due to Availability of
Numeric Support and LTS. Where we can get Some Support from Apache Beam Team.
Note: But when we use Custom Class then it's Working Fine As Expected.
> Beam Performance Degradation on Dataflow Runner
> -----------------------------------------------
>
> Key: BEAM-6846
> URL: https://issues.apache.org/jira/browse/BEAM-6846
> Project: Beam
> Issue Type: Improvement
> Components: runner-dataflow
> Affects Versions: 2.7.0, 2.8.0
> Reporter: Kishan Kumar
> Priority: Major
> Labels: patch
> Fix For: 2.12.0
>
>
> After Upgrading From 2.5.0 Version the jobs of Version 2.7.0 are taking a
> long time compared to 2.5.0.
> System Lag is also got introduced the Error Getting Generated:
> "Workflow failed. Causes: The Dataflow job appears to be stuck because no
> worker activity has been seen in the last 1h."
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
