[
https://issues.apache.org/jira/browse/BEAM-10458?focusedWorklogId=462727&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-462727
]
ASF GitHub Bot logged work on BEAM-10458:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 23/Jul/20 22:08
Start Date: 23/Jul/20 22:08
Worklog Time Spent: 10m
Work Description: tvalentyn commented on pull request #12228:
URL: https://github.com/apache/beam/pull/12228#issuecomment-663256339
Good catch, @charlesccychen
----------------------------------------------------------------
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: 462727)
Time Spent: 40m (was: 0.5h)
> Message limit for grpc message is set to default 4 MB
> -----------------------------------------------------
>
> Key: BEAM-10458
> URL: https://issues.apache.org/jira/browse/BEAM-10458
> Project: Beam
> Issue Type: Bug
> Components: sdk-py-harness
> Affects Versions: 2.22.0
> Reporter: Keshav
> Assignee: Keshav
> Priority: P2
> Time Spent: 40m
> Remaining Estimate: 0h
>
> The default limit of a grpc message is set low to 4 MB, and is not overridden
> in the sdk_worker.py for the _control_channel. This was first discovered when
> submitting a beam job via a flink operator orchestrated by kubernetes
> ([https://github.com/GoogleCloudPlatform/flink-on-k8s-operator)|https://github.com/GoogleCloudPlatform/flink-on-k8s-operator].
> This issue was resolved for apache-beam==2.18 in BEAM-10334, but exists in
> apache-beam==2.22 (and presumably all versions 2.17 onwards).
>
> This can be fixed by modifying the options parameter to allow any size grpc
> message to be sent or received.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)