[
https://issues.apache.org/jira/browse/BEAM-10458?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17223060#comment-17223060
]
Beam JIRA Bot commented on BEAM-10458:
--------------------------------------
This issue is P2 but has been unassigned without any comment for 60 days so it
has been labeled "stale-P2". If this issue is still affecting you, we care!
Please comment and remove the label. Otherwise, in 14 days the issue will be
moved to P3.
Please see https://beam.apache.org/contribute/jira-priorities/ for a detailed
explanation of what these priorities mean.
> 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
> Priority: P2
> Labels: stale-P2
> Time Spent: 1h
> 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)
