[ 
https://issues.apache.org/jira/browse/BEAM-5853?focusedWorklogId=158946&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-158946
 ]

ASF GitHub Bot logged work on BEAM-5853:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 26/Oct/18 01:07
            Start Date: 26/Oct/18 01:07
    Worklog Time Spent: 10m 
      Work Description: boyuanzz opened a new pull request #6837: [BEAM-5853] 
Possible fix
URL: https://github.com/apache/beam/pull/6837
 
 
   I'm not sure whether this is a right fix but seems like it works for me to 
stop the stuckness. 
   R: @robertwb, @lukecwik 
   More information:
   For the stuck fnapi worker pipeline, it gets stuck at 
[maybeWait](https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/worker/src/main/java/org/apache/beam/runners/dataflow/worker/fn/data/RemoteGrpcPortWriteOperation.java#L165),
 and keeps evaluating 
[shouldWait](https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/worker/src/main/java/org/apache/beam/runners/dataflow/worker/fn/data/RemoteGrpcPortWriteOperation.java#L111).
 I found, the numProcessed should be -1 since it's not supported and the 
targetElementsSent should be set to MAX. But the [following else 
block](https://github.com/apache/beam/blob/master/runners/google-cloud-dataflow-java/worker/src/main/java/org/apache/beam/runners/dataflow/worker/fn/data/RemoteGrpcPortWriteOperation.java#L129)
 will override this logic again, which causes this loop forever.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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: 158946)
            Time Spent: 10m
    Remaining Estimate: 0h

> PR6752 cause WindowedWordCount fn-api worker pipeline stuck
> -----------------------------------------------------------
>
>                 Key: BEAM-5853
>                 URL: https://issues.apache.org/jira/browse/BEAM-5853
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-dataflow, sdk-java-harness
>            Reporter: Boyuan Zhang
>            Assignee: Robert Bradshaw
>            Priority: Major
>         Attachments: log.png, log1.png
>
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> [https://github.com/apache/beam/pull/6752] caused fn-api worker windowed 
> wordcount pipeline got stucked in sdk harness:



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to