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

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

                Author: ASF GitHub Bot
            Created on: 20/Feb/20 20:04
            Start Date: 20/Feb/20 20:04
    Worklog Time Spent: 10m 
      Work Description: ibzib commented on pull request #10916: [BEAM-9225] Fix 
Flink uberjar job termination bug.
URL: https://github.com/apache/beam/pull/10916#discussion_r382228673
 
 

 ##########
 File path: 
sdks/python/apache_beam/runners/portability/flink_uber_jar_job_server.py
 ##########
 @@ -202,8 +202,10 @@ def _state_iter():
       sleep_secs = 1.0
       while True:
         current_state, timestamp = self._get_state()
-        if timestamp is not None:
-          # non-None indicates that the state has changed
+        if timestamp is None:
 
 Review comment:
   Done
 
----------------------------------------------------------------
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: 390209)
    Time Spent: 40m  (was: 0.5h)

> Flink uber jar job server hangs
> -------------------------------
>
>                 Key: BEAM-9225
>                 URL: https://issues.apache.org/jira/browse/BEAM-9225
>             Project: Beam
>          Issue Type: Bug
>          Components: runner-flink
>            Reporter: Kyle Weaver
>            Assignee: Kyle Weaver
>            Priority: Major
>              Labels: portability-flink
>             Fix For: 2.20.0
>
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> This was observed on Kubernetes. I suspect this behavior might also be the 
> reason beam_PostCommit_PortableJar_Flink is timing out.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

Reply via email to