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

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

                Author: ASF GitHub Bot
            Created on: 12/Mar/19 17:51
            Start Date: 12/Mar/19 17:51
    Worklog Time Spent: 10m 
      Work Description: rohdesamuel commented on issue #8012: [BEAM-6777] Add 
HealthDaemon and tests
URL: https://github.com/apache/beam/pull/8012#issuecomment-472110777
 
 
   > Is the expectation that this will ping an endpoint hosted by dataflow 
service or the runner harness?
   
   Neither, this will ping the existing Healthchecker sibling container that 
already sends health checks to Dataflow. The Healthchecker container will then 
communicate the health to the Dataflow service.
 
----------------------------------------------------------------
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: 211906)
    Time Spent: 1h 50m  (was: 1h 40m)

> SDK Harness Resilience
> ----------------------
>
>                 Key: BEAM-6777
>                 URL: https://issues.apache.org/jira/browse/BEAM-6777
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-dataflow
>            Reporter: Sam Rohde
>            Assignee: Sam Rohde
>            Priority: Major
>          Time Spent: 1h 50m
>  Remaining Estimate: 0h
>
> If the Python SDK Harness crashes in any way (user code exception, OOM, etc) 
> the job will hang and waste resources. The fix is to add a daemon in the SDK 
> Harness and Runner Harness to communicate with Dataflow to restart the VM 
> when stuckness is detected.



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

Reply via email to