See <https://ci-beam.apache.org/job/beam_LoadTests_Java_GBK_Dataflow_V2_Streaming_Java17/409/display/redirect?page=changes>
Changes: [noreply] Add sideinputs to the RunInference Transform (#25200) [noreply] Move changes to correct release in CHANGES.md (#25288) [noreply] Pass instead of raising an error (#25287) [noreply] [WebSite] Add new Python quickstart (#24804) [noreply] [CdapIO] Implement windowed write (#25206) [noreply] [Spark Dataset runner] Fix collection encoder bug that may lead to [noreply] [Spark Dataset runner] Break linage of dataset to reduce Spark planning ------------------------------------------ [...truncated 423.19 KB...] > Task :sdks:java:io:kafka:classes UP-TO-DATE > Task :sdks:java:container:java17:copySdkHarnessLauncher Execution optimizations have been disabled for task ':sdks:java:container:java17:copySdkHarnessLauncher' to ensure correctness due to the following reasons: - Gradle detected a problem with the following location: '<https://ci-beam.apache.org/job/beam_LoadTests_Java_GBK_Dataflow_V2_Streaming_Java17/ws/src/sdks/java/container/build/target'.> Reason: Task ':sdks:java:container:java17:copySdkHarnessLauncher' uses this output of task ':sdks:java:container:downloadCloudProfilerAgent' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. - Gradle detected a problem with the following location: '<https://ci-beam.apache.org/job/beam_LoadTests_Java_GBK_Dataflow_V2_Streaming_Java17/ws/src/sdks/java/container/build/target'.> Reason: Task ':sdks:java:container:java17:copySdkHarnessLauncher' uses this output of task ':sdks:java:container:pullLicenses' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.5.1/userguide/validation_problems.html#implicit_dependency for more details about this problem. > Task :sdks:java:extensions:google-cloud-platform-core:jar UP-TO-DATE > Task :sdks:java:io:kafka:jar UP-TO-DATE > Task :sdks:java:container:java17:copyDockerfileDependencies UP-TO-DATE > Task :sdks:java:io:google-cloud-platform:compileJava UP-TO-DATE > Task :sdks:java:io:google-cloud-platform:classes UP-TO-DATE > Task :sdks:java:io:google-cloud-platform:jar UP-TO-DATE > Task :sdks:java:testing:load-tests:compileJava UP-TO-DATE > Task :sdks:java:testing:load-tests:classes UP-TO-DATE > Task :sdks:java:testing:load-tests:jar UP-TO-DATE > Task :runners:google-cloud-dataflow-java:compileJava UP-TO-DATE > Task :runners:google-cloud-dataflow-java:classes UP-TO-DATE > Task :runners:google-cloud-dataflow-java:jar UP-TO-DATE > Task :sdks:java:container:java17:dockerPrepare > Task :sdks:java:container:java17:docker > Task :runners:google-cloud-dataflow-java:buildAndPushDockerJavaContainer WARNING: `gcloud docker` will not be supported for Docker client versions above 18.03. As an alternative, use `gcloud auth configure-docker` to configure `docker` to use `gcloud` as a credential helper, then use `docker` as you would for non-GCR registries, e.g. `docker pull gcr.io/project-id/my-image`. Add `--verbosity=error` to silence this warning: `gcloud docker --verbosity=error -- pull gcr.io/project-id/my-image`. See: https://cloud.google.com/container-registry/docs/support/deprecation-notices#gcloud-docker The push refers to repository [us.gcr.io/apache-beam-testing/java-postcommit-it/java] 3c1583bfe2c7: Preparing a21480301a5b: Preparing 4d16ccc968f2: Preparing 6572e4a7b32b: Preparing 65cd2718713c: Preparing b9febfc79d42: Preparing e913a7e9dbbb: Preparing 848ddde9a078: Preparing 15dd09d20bfa: Preparing 96e4424b209a: Preparing 0c72272651b9: Preparing 0719cbd34b1c: Preparing d237b2d0c97d: Preparing 4c811427227a: Preparing 78f0ae85c8a9: Preparing 933b8a4d8c98: Preparing 3bc383470c05: Preparing e93827457889: Preparing 65cd2718713c: Waiting 08fa02ce37eb: Preparing a037458de4e0: Preparing b9febfc79d42: Waiting bafdbe68e4ae: Preparing a13c519c6361: Preparing e913a7e9dbbb: Waiting 848ddde9a078: Waiting 96e4424b209a: Waiting 15dd09d20bfa: Waiting a037458de4e0: Waiting 0c72272651b9: Waiting 3bc383470c05: Waiting bafdbe68e4ae: Waiting e93827457889: Waiting 0719cbd34b1c: Waiting a13c519c6361: Waiting 4c811427227a: Waiting d237b2d0c97d: Waiting 08fa02ce37eb: Waiting 933b8a4d8c98: Waiting 4d16ccc968f2: Pushed 6572e4a7b32b: Pushed a21480301a5b: Pushed 3c1583bfe2c7: Pushed e913a7e9dbbb: Pushed 65cd2718713c: Pushed 848ddde9a078: Pushed b9febfc79d42: Pushed 96e4424b209a: Pushed 0719cbd34b1c: Pushed 15dd09d20bfa: Pushed 0c72272651b9: Pushed d237b2d0c97d: Pushed 3bc383470c05: Layer already exists e93827457889: Layer already exists 08fa02ce37eb: Layer already exists a037458de4e0: Layer already exists bafdbe68e4ae: Layer already exists a13c519c6361: Layer already exists 4c811427227a: Pushed 78f0ae85c8a9: Pushed 933b8a4d8c98: Pushed 20230203152244: digest: sha256:6fc6f7c8254d2faf380ffc7f1ca979b460b1d17d1d690fe771535756b02cea35 size: 4934 > Task :sdks:java:testing:load-tests:run Feb 03, 2023 3:23:12 PM org.apache.beam.runners.dataflow.options.DataflowPipelineOptions$StagingLocationFactory create INFO: No stagingLocation provided, falling back to gcpTempLocation Feb 03, 2023 3:23:13 PM org.apache.beam.runners.dataflow.DataflowRunner fromOptions INFO: PipelineOptions.filesToStage was not specified. Defaulting to files from the classpath: will stage 232 files. Enable logging at DEBUG level to see which files will be staged. Feb 03, 2023 3:23:13 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Executing pipeline on the Dataflow Service, which will have billing implications related to Google Compute Engine usage and other Google Cloud Services. Feb 03, 2023 3:23:15 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements INFO: Uploading 232 files from PipelineOptions.filesToStage to staging location to prepare for execution. Feb 03, 2023 3:23:16 PM org.apache.beam.runners.dataflow.util.PackageUtil stageClasspathElements INFO: Staging files complete: 232 files cached, 0 files newly uploaded in 0 seconds Feb 03, 2023 3:23:16 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Staging portable pipeline proto to gs://temp-storage-for-perf-tests/loadtests/staging/ Feb 03, 2023 3:23:16 PM org.apache.beam.runners.dataflow.util.PackageUtil tryStagePackage INFO: Uploading <101776 bytes, hash 59ff7e6cee38c7fd0a08642b27a42ee9ad84d31b82e2b9c88ccd18fb432920a4> to gs://temp-storage-for-perf-tests/loadtests/staging/pipeline-Wf9-bO44x_0KCGQrJ6Qu6a2E0xuC4rnIjM0Y-0MpIKQ.pb Feb 03, 2023 3:23:18 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Read input/DataflowRunner.StreamingUnboundedRead.ReadWithIds as step s1 Feb 03, 2023 3:23:18 PM org.apache.beam.sdk.io.synthetic.SyntheticUnboundedSource split INFO: Split into 20 bundles: [SyntheticUnboundedSource{startOffset=0, endOffset=1000000}, SyntheticUnboundedSource{startOffset=1000000, endOffset=2000000}, SyntheticUnboundedSource{startOffset=2000000, endOffset=3000000}, SyntheticUnboundedSource{startOffset=3000000, endOffset=4000000}, SyntheticUnboundedSource{startOffset=4000000, endOffset=5000000}, SyntheticUnboundedSource{startOffset=5000000, endOffset=6000000}, SyntheticUnboundedSource{startOffset=6000000, endOffset=7000000}, SyntheticUnboundedSource{startOffset=7000000, endOffset=8000000}, SyntheticUnboundedSource{startOffset=8000000, endOffset=9000000}, SyntheticUnboundedSource{startOffset=9000000, endOffset=10000000}, SyntheticUnboundedSource{startOffset=10000000, endOffset=11000000}, SyntheticUnboundedSource{startOffset=11000000, endOffset=12000000}, SyntheticUnboundedSource{startOffset=12000000, endOffset=13000000}, SyntheticUnboundedSource{startOffset=13000000, endOffset=14000000}, SyntheticUnboundedSource{startOffset=14000000, endOffset=15000000}, SyntheticUnboundedSource{startOffset=15000000, endOffset=16000000}, SyntheticUnboundedSource{startOffset=16000000, endOffset=17000000}, SyntheticUnboundedSource{startOffset=17000000, endOffset=18000000}, SyntheticUnboundedSource{startOffset=18000000, endOffset=19000000}, SyntheticUnboundedSource{startOffset=19000000, endOffset=20000000}] Feb 03, 2023 3:23:18 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Read input/StripIds as step s2 Feb 03, 2023 3:23:18 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Collect start time metrics as step s3 Feb 03, 2023 3:23:18 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Total bytes monitor as step s4 Feb 03, 2023 3:23:18 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Window.Into()/Window.Assign as step s5 Feb 03, 2023 3:23:18 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Group by key (0) as step s6 Feb 03, 2023 3:23:18 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Ungroup and reiterate (0) as step s7 Feb 03, 2023 3:23:18 PM org.apache.beam.runners.dataflow.DataflowPipelineTranslator$Translator addStep INFO: Adding Collect end time metrics (0) as step s8 Feb 03, 2023 3:23:18 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Dataflow SDK version: 2.46.0-SNAPSHOT Feb 03, 2023 3:23:19 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: To access the Dataflow monitoring console, please navigate to https://console.cloud.google.com/dataflow/jobs/us-central1/2023-02-03_07_23_18-7033659673023174795?project=apache-beam-testing Feb 03, 2023 3:23:19 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: Submitted job: 2023-02-03_07_23_18-7033659673023174795 Feb 03, 2023 3:23:19 PM org.apache.beam.runners.dataflow.DataflowRunner run INFO: To cancel the job using the 'gcloud' tool, run: > gcloud dataflow jobs --project=apache-beam-testing cancel > --region=us-central1 2023-02-03_07_23_18-7033659673023174795 Feb 03, 2023 3:23:32 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process WARNING: 2023-02-03T15:23:26.776Z: The workflow name is not a valid Cloud Label. Labels applied to Cloud resources (such as GCE Instances) for monitoring will be labeled with this modified job name: load0tests0java170dataflow0v20streaming0gbk07-jenkins-0203-p549. For the best monitoring experience, please name your job with a valid Cloud Label. For details, see: https://cloud.google.com/compute/docs/labeling-resources#restrictions Feb 03, 2023 3:23:38 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:38.499Z: Worker configuration: e2-standard-2 in us-central1-b. Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:39.853Z: Expanding SplittableParDo operations into optimizable parts. Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:39.876Z: Expanding CollectionToSingleton operations into optimizable parts. Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:39.938Z: Expanding CoGroupByKey operations into optimizable parts. Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.004Z: Expanding SplittableProcessKeyed operations into optimizable parts. Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.034Z: Expanding GroupByKey operations into streaming Read/Write steps Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.101Z: Lifting ValueCombiningMappingFns into MergeBucketsMappingFns Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.199Z: Fusing adjacent ParDo, Read, Write, and Flatten operations Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.224Z: Fusing consumer Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) into Read input/Impulse Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.257Z: Fusing consumer Read-input-ParDo-UnboundedSourceAsSDFWrapper--ParMultiDo-UnboundedSourceAsSDFWrapper-/PairWithRestriction into Read input/ParDo(OutputSingleSource)/ParMultiDo(OutputSingleSource) Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.287Z: Fusing consumer Read-input-ParDo-UnboundedSourceAsSDFWrapper--ParMultiDo-UnboundedSourceAsSDFWrapper-/SplitWithSizing into Read-input-ParDo-UnboundedSourceAsSDFWrapper--ParMultiDo-UnboundedSourceAsSDFWrapper-/PairWithRestriction Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.325Z: Fusing consumer Read input/ParDo(StripIds)/ParMultiDo(StripIds) into Read-input-ParDo-UnboundedSourceAsSDFWrapper--ParMultiDo-UnboundedSourceAsSDFWrapper-/ProcessElementAndRestrictionWithSizing Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.358Z: Fusing consumer Collect start time metrics/ParMultiDo(TimeMonitor) into Read input/ParDo(StripIds)/ParMultiDo(StripIds) Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.394Z: Fusing consumer Total bytes monitor/ParMultiDo(ByteMonitor) into Collect start time metrics/ParMultiDo(TimeMonitor) Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.420Z: Fusing consumer Window.Into()/Window.Assign into Total bytes monitor/ParMultiDo(ByteMonitor) Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.449Z: Fusing consumer Group by key (0)/WriteStream into Window.Into()/Window.Assign Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.478Z: Fusing consumer Group by key (0)/MergeBuckets into Group by key (0)/ReadStream Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.502Z: Fusing consumer Ungroup and reiterate (0)/ParMultiDo(UngroupAndReiterate) into Group by key (0)/MergeBuckets Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.529Z: Fusing consumer Collect end time metrics (0)/ParMultiDo(TimeMonitor) into Ungroup and reiterate (0)/ParMultiDo(UngroupAndReiterate) Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:40.606Z: Running job using Streaming Engine Feb 03, 2023 3:23:41 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:41.086Z: Starting 5 ****s in us-central1-b... Feb 03, 2023 3:23:59 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:23:58.734Z: Your project already contains 100 Dataflow-created metric descriptors, so new user metrics of the form custom.googleapis.com/* will not be created. However, all user metrics are also available in the metric dataflow.googleapis.com/job/user_counter. If you rely on the custom metrics, you can delete old / unused metric descriptors. See https://developers.google.com/apis-explorer/#p/monitoring/v3/monitoring.projects.metricDescriptors.list and https://developers.google.com/apis-explorer/#p/monitoring/v3/monitoring.projects.metricDescriptors.delete Feb 03, 2023 3:24:14 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:24:12.859Z: Autoscaling: Raised the number of ****s to 1 so that the pipeline can catch up with its backlog and keep up with its input rate. Feb 03, 2023 3:24:14 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:24:12.878Z: Autoscaling: Resized **** pool to 1, though goal was 5. This could be a quota issue. Feb 03, 2023 3:24:22 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:24:22.507Z: Autoscaling: Raised the number of ****s to 5 so that the pipeline can catch up with its backlog and keep up with its input rate. Feb 03, 2023 3:25:31 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:25:29.372Z: All ****s have finished the startup processes and began to receive work requests. Feb 03, 2023 3:25:33 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:25:32.012Z: Workers have started successfully. Feb 03, 2023 3:30:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:30:54.175Z: Cleaning up. Feb 03, 2023 3:30:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:30:54.278Z: Stopping **** pool... Feb 03, 2023 3:30:54 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:30:54.345Z: Stopping **** pool... Feb 03, 2023 3:33:14 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:33:13.150Z: Autoscaling: Reduced the number of ****s to 0 based on low average **** CPU utilization, and the pipeline having sufficiently low backlog and keeping up with input rate. Feb 03, 2023 3:33:14 PM org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process INFO: 2023-02-03T15:33:13.196Z: Worker pool stopped. Feb 03, 2023 3:33:19 PM org.apache.beam.runners.dataflow.DataflowPipelineJob logTerminalState INFO: Job 2023-02-03_07_23_18-7033659673023174795 finished with status DONE. Load test results for test (ID): 12e4f626-e35a-49c3-bb05-6c0b50e53060 and timestamp: 2023-02-03T15:23:13.432000000Z: Metric: Value: dataflow_v2_java17_runtime_sec 224.075 dataflow_v2_java17_total_bytes_count 1.999998E9 > Task :runners:google-cloud-dataflow-java:cleanUpDockerJavaImages FAILED Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20230203152244 Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:6fc6f7c8254d2faf380ffc7f1ca979b460b1d17d1d690fe771535756b02cea35 ERROR: (gcloud.container.images.untag) Image could not be found: [us.gcr.io/apache-beam-testing/java-postcommit-it/java:20230203152244] FAILURE: Build failed with an exception. * Where: Build file '<https://ci-beam.apache.org/job/beam_LoadTests_Java_GBK_Dataflow_V2_Streaming_Java17/ws/src/runners/google-cloud-dataflow-java/build.gradle'> line: 301 * What went wrong: Execution failed for task ':runners:google-cloud-dataflow-java:cleanUpDockerJavaImages'. > Process 'command 'gcloud'' finished with non-zero exit value 1 * Try: > Run with --stacktrace option to get the stack trace. > Run with --info or --debug option to get more log output. * Get more help at https://help.gradle.org Deprecated Gradle features were used in this build, making it incompatible with Gradle 8.0. You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins. See https://docs.gradle.org/7.5.1/userguide/command_line_interface.html#sec:command_line_warnings Execution optimizations have been disabled for 1 invalid unit(s) of work during this build to ensure correctness. Please consult deprecation warnings for more details. BUILD FAILED in 11m 1s 108 actionable tasks: 9 executed, 99 up-to-date Publishing build scan... https://gradle.com/s/qwzuele5gksak Build step 'Invoke Gradle script' changed build result to FAILURE Build step 'Invoke Gradle script' marked build as failure --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
