[
https://issues.apache.org/jira/browse/BEAM-6166?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17174807#comment-17174807
]
Beam JIRA Bot commented on BEAM-6166:
-------------------------------------
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.
> Allow Runners to configure parallelism of GrpcStateService
> ----------------------------------------------------------
>
> Key: BEAM-6166
> URL: https://issues.apache.org/jira/browse/BEAM-6166
> Project: Beam
> Issue Type: Improvement
> Components: runner-core
> Reporter: Maximilian Michels
> Priority: P2
> Labels: stale-P2
>
> GrpcStateService by default uses a non-thread-safe OutboundServer which has
> led to problem with asynchronously sending data to it. The sending is now
> changed to be done synchronously but it could be done asynchronously if
> OutboundObserverFactory was used.
> Depending on the Runner, asynchronicity may or may not be desired. We should
> provide a way to configure parallelism of GrpcStateService for each Runner.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
