Ilya Kozyrev created BEAM-13033:
-----------------------------------
Summary: Go context for executor
Key: BEAM-13033
URL: https://issues.apache.org/jira/browse/BEAM-13033
Project: Beam
Issue Type: New Feature
Components: beam-playground
Reporter: Ilya Kozyrev
Go context usage
As a *maintainer*,
I want to be able to control all goroutines using the Go context.
Acceptance criteria:
1. Context with Deadline is provided for the executor processes
*Scenario*: Pipeline was stuck
{color:#FF0000}Given{color}: User sent RunCode request
{color:#FF0000}When{color}: Server compiled code
{color:#FF0000}And{color}: Server ran compiled code
{color:#FF0000}And{color}: Code didn't complete in deadline time
{color:#FF0000}Then{color}: All executor processes is cancel
{color:#FF0000}And{color}: All resources cleaned up
{color:#FF0000}And{color}: Pipeline status changed to failed
{color:#FF0000}And{color}: Correspondent error retrieved to the client (through
cache)
2. Context with cancelation is provided for the executor processes
*Scenario*: User closed Playground
{color:#FF0000}Given{color}: User sent RunCode request
{color:#FF0000}When{color}: Server compiled code
{color:#FF0000}And{color}: Server ran compiled code
{color:#FF0000}And{color}: Client went away from Playground page
{color:#FF0000}Then{color}: All executor processes is cancel
{color:#FF0000}And{color}: All resources cleaned up
{color:#FF0000}And{color}: Pipeline status changed to failed
{color:#FF0000}And{color}: Correspondent error put to cache.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
