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

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

                Author: ASF GitHub Bot
            Created on: 24/Feb/22 17:04
            Start Date: 24/Feb/22 17:04
    Worklog Time Spent: 10m 
      Work Description: aaltay commented on pull request #16741:
URL: https://github.com/apache/beam/pull/16741#issuecomment-1050066353


   colab users are reporting error logs showing "No cluster_manager is 
associated with the provided pipeline!". Could you please file a bug / fix the 
problem?


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Issue Time Tracking
-------------------

    Worklog Id:     (was: 732501)
    Time Spent: 29h 40m  (was: 29.5h)

> Integrate DataprocClusterManager into Interactive Environment
> -------------------------------------------------------------
>
>                 Key: BEAM-13812
>                 URL: https://issues.apache.org/jira/browse/BEAM-13812
>             Project: Beam
>          Issue Type: New Feature
>          Components: runner-py-interactive
>            Reporter: Victor Chen
>            Assignee: Victor Chen
>            Priority: P2
>             Fix For: Not applicable
>
>          Time Spent: 29h 40m
>  Remaining Estimate: 0h
>
> * Integrates the DataprocClusterManager previously introduced in:
>  ** BEAM-13799 Create an Interactive Beam Dataproc package for users to 
> manage clusters with
>  * Adds code to automatically create a Dataproc cluster configured with 
> Docker and Flink if a user instantiates an InteractiveRunner using 
> underlying_runner='FlinkRunner'
>  * By default, the created Dataproc cluster will be called 
> 'interactive-beam-cluster' and will be cleaned up when the Interactive 
> Environment is interrupted
>  * Introduces the Clusters class in interactive_beam.py, which acts as a user 
> interface that provides the user with the following capabilities:
>  ** Changing the default name of the clusters created by Interactive Beam
>  ** Cleaning up a cluster by providing a corresponding pipeline, an option to 
> force the deletion is provided, in the case where more than one pipeline use 
> the same cluster
>  ** Getting all pipelines that use the provided master_url
>  ** Receiving a description back for either the cluster corresponding to a 
> specific pipeline, or the descriptions of all pipelines



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

Reply via email to