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

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

                Author: ASF GitHub Bot
            Created on: 07/Jun/19 16:15
            Start Date: 07/Jun/19 16:15
    Worklog Time Spent: 10m 
      Work Description: lgajowy commented on pull request #8636: [BEAM-7368] 
Flink + Python + gbk load test
URL: https://github.com/apache/beam/pull/8636#discussion_r291661268
 
 

 ##########
 File path: .test-infra/dataproc/create_flink_cluster.sh
 ##########
 @@ -57,6 +59,10 @@ 
DOCKER_INIT="$GCS_BUCKET/$INIT_ACTIONS_FOLDER_NAME/docker.sh"
 
 # Flink properties
 FLINK_LOCAL_PORT=8081
+
+# By default each taskmanager has one slot - use that value to avoid sharing 
SDK Harness by multiple tasks.
+FLINK_TASKMANAGER_SLOTS="${FLINK_TASKMANAGER_SLOTS:=1}"
 
 Review comment:
   parralelism = 5, there are 5 Dataproc workers but I just found out that the 
flink.sh init action creates 4 task_managers. I think this is the culprit. I 
will take a look later.
 
----------------------------------------------------------------
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: 256019)
    Time Spent: 9h 20m  (was: 9h 10m)

> Run Python GBK load tests on portable Flink runner
> --------------------------------------------------
>
>                 Key: BEAM-7368
>                 URL: https://issues.apache.org/jira/browse/BEAM-7368
>             Project: Beam
>          Issue Type: Sub-task
>          Components: testing
>            Reporter: Lukasz Gajowy
>            Assignee: Lukasz Gajowy
>            Priority: Major
>          Time Spent: 9h 20m
>  Remaining Estimate: 0h
>




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

Reply via email to