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

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

                Author: ASF GitHub Bot
            Created on: 06/Sep/19 20:45
            Start Date: 06/Sep/19 20:45
    Worklog Time Spent: 10m 
      Work Description: lostluck commented on issue #9504: [BEAM-8166] Allow in 
process workers to exit without killing the process.
URL: https://github.com/apache/beam/pull/9504#issuecomment-529008251
 
 
   Excellent question, and you're correct the new mode isn't presently 
available for any public runners at this time. Flink, Spark, Dataflow all rely 
on containers, which don't run into this.
   
   However, native Go runners might choose to make different calls, or runners 
where the runner half a worker is linked into the same binary run into this, 
such as the internal Google runner I work on uses. It has an inprocess mode 
that can take advantage of this as well.
 
----------------------------------------------------------------
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: 308145)
    Time Spent: 40m  (was: 0.5h)

> Support Graceful shutdown of worker harness.
> --------------------------------------------
>
>                 Key: BEAM-8166
>                 URL: https://issues.apache.org/jira/browse/BEAM-8166
>             Project: Beam
>          Issue Type: Improvement
>          Components: runner-core, sdk-go
>            Reporter: Robert Burke
>            Priority: Minor
>          Time Spent: 40m
>  Remaining Estimate: 0h
>
> Ideally there should be a clear Shutdown control RPC a runner can send a 
> worker harness to trigger an orderly shutdown.
> Absent that, errors on the runner side shouldn't manifest as SDK worker 
> harness errors. SDKs should log, and gracefully shutdown from GRPC errors.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

Reply via email to