See
<https://ci-beam.apache.org/job/beam_LoadTests_Java_GBK_Dataflow_V2_Streaming_Java11/236/display/redirect?page=changes>
Changes:
[noreply] Update README.md
[marco.robles] Update README with latest PreCommit Jobs
[marco.robles] Update Postcommit jobs with latest jobs
[marco.robles] Update Performace job tests in readme
[marco.robles] update load job tests with latest updates
[marco.robles] update other jobs test with latest updates
[marco.robles] mismatch links fix
[marco.robles] update trigger phrase for some postCommit jobs
[marco.robles] correct trigger phrases in readme
[marco.robles] add pending jobs to readme
[noreply] Update README.md
[mmack] [BEAM-13246] Add support for S3 Bucket Key at the object level (AWS Sdk
[Pablo Estrada] Output successful rows from BQ Streaming Inserts
[schapman] BEAM-13439 Type annotation for ptransform_fn
[noreply] [BEAM-13606] Fail bundles with failed BigTable mutations (#16751)
[mmack] [adhoc] Remove remaining usage of Powermock from aws2.
[marco.robles] fix broken links in jobs & remove the invalid ones
[Kyle Weaver] Update Dataflow Python dev container images.
[Kiley Sok] Add java 17 to changes
[noreply] [BEAM-12914] Add missing 3.9 opcodes to type inference. (#16761)
[noreply] [BEAM-13321] Initial BigQueryIO externalization. (#16489)
[noreply] [BEAM-13193] Enable process bundle response elements embedding in Java
[noreply] [BEAM-13830] added a debeziumio_expansion_addr flag to GoSDK (#16780)
[noreply] Apply spotless. (#16783)
[Daniel Oliveira] [BEAM-13732] Switch x-lang BigQueryIO expansion service to
GCP one.
[noreply] [BEAM-13858] Fix broken github action on :sdks:go:examples:wordCount
[Kiley Sok] add jira for runner v2
[noreply] [BEAM-13732] Go SDK BigQuery IO wrapper. Initial implementation.
[noreply] [BEAM-13732] Add example for Go BigQuery IO wrapper. (#16786)
[noreply] Update CHANGES.md with Go SDK milestones. (#16787)
[noreply] [BEAM-13193] Allow BeamFnDataOutboundObserver to flush elements.
------------------------------------------
[...truncated 70.08 KB...]
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
generic::cancelled: Data channel closed, unable to receive additional data from
SDK sdk-0-0
passed through:
==>
dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
Feb 09, 2022 1:47:10 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T13:47:08.959Z: 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 09, 2022 1:49:23 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T13:49:22.717Z: 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 09, 2022 1:53:15 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T13:53:14.999Z: 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 09, 2022 1:54:19 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T13:54:19.723Z: 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 09, 2022 1:55:22 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T13:55:21.389Z: 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 09, 2022 1:57:27 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T13:57:26.097Z: 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 09, 2022 2:03:26 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:03:26.524Z: 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 09, 2022 2:04:29 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:04:27.936Z: 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 09, 2022 2:05:34 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:05:32.931Z: 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 09, 2022 2:06:31 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:06:31.284Z: 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 09, 2022 2:07:35 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:07:35.167Z: 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 09, 2022 2:11:42 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:11:40.699Z: 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 09, 2022 2:13:41 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:13:40.599Z: 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 09, 2022 2:14:44 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:14:43.913Z: 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 09, 2022 2:15:49 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:15:48.554Z: 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 09, 2022 2:19:49 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:19:49.318Z: 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 09, 2022 2:20:56 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:20:56.714Z: 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 09, 2022 2:21:56 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:21:54.631Z: 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 09, 2022 2:24:01 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:23:59.372Z: 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 09, 2022 2:24:59 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:24:58.716Z: 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 09, 2022 2:30:16 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:30:14.370Z: 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 09, 2022 2:32:07 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:32:06.249Z: 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 09, 2022 2:33:12 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:33:11.490Z: 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 09, 2022 2:38:13 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:38:12.312Z: 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 09, 2022 2:39:18 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:39:17.462Z: 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 09, 2022 2:40:21 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:40:18.385Z: 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 09, 2022 2:41:25 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:41:23.658Z: 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 09, 2022 2:46:25 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:46:24.189Z: 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 09, 2022 2:48:26 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:48:25.154Z: 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 09, 2022 2:50:30 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:50:28.603Z: 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 09, 2022 2:51:30 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:51:28.120Z: 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 09, 2022 2:54:35 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:54:33.396Z: 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 09, 2022 2:56:35 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:56:34.335Z: 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 09, 2022 2:58:38 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:58:37.645Z: 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 09, 2022 2:59:43 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T14:59:42.439Z: 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 09, 2022 3:02:45 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:02:44.261Z: 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 09, 2022 3:04:49 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:04:49.240Z: 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 09, 2022 3:06:50 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:06:50.512Z: 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 09, 2022 3:07:54 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:07:53.640Z: 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 09, 2022 3:11:08 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:11:07.850Z: 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 09, 2022 3:13:00 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:12:58.006Z: 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 09, 2022 3:15:04 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:15:03.088Z: 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 09, 2022 3:16:08 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:16:06.608Z: 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 09, 2022 3:19:07 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:19:06.988Z: 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 09, 2022 3:21:12 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:21:12.508Z: 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 09, 2022 3:24:15 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:24:14.709Z: 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 09, 2022 3:27:23 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:27:21.793Z: 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 09, 2022 3:28:21 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:28:21.398Z: 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 09, 2022 3:29:21 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:29:21.275Z: 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 09, 2022 3:32:27 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:32:26.464Z: 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 09, 2022 3:36:28 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:36:27.434Z: 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 09, 2022 3:37:33 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:37:32.283Z: 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 09, 2022 3:38:33 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:38:32.127Z: 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 09, 2022 3:40:38 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:40:38.082Z: 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 09, 2022 3:44:44 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:44:42.216Z: 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 09, 2022 3:45:45 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:45:43.503Z: 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 09, 2022 3:46:48 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:46:47.365Z: 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 09, 2022 3:48:47 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:48:46.083Z: 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 09, 2022 3:52:51 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:52:50.574Z: 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 09, 2022 3:53:54 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:53:54.316Z: 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 09, 2022 3:55:00 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:54:58.743Z: 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 09, 2022 3:56:58 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T15:56:56.920Z: 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 09, 2022 4:00:41 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T16:00:41.111Z: Cancel request is committed for workflow job:
2022-02-09_04_27_38-11726103238141430929.
Feb 09, 2022 4:00:41 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T16:00:41.145Z: Cleaning up.
Feb 09, 2022 4:00:41 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T16:00:41.219Z: Stopping **** pool...
Feb 09, 2022 4:00:44 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T16:00:43.384Z: Stopping **** pool...
Feb 09, 2022 4:03:40 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T16:03:39.518Z: 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 09, 2022 4:03:40 PM
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-02-09T16:03:39.551Z: Worker pool stopped.
Feb 09, 2022 4:03:46 PM org.apache.beam.runners.dataflow.DataflowPipelineJob
logTerminalState
INFO: Job 2022-02-09_04_27_38-11726103238141430929 finished with status
CANCELLED.
Load test results for test (ID): ad3238c4-9571-423d-86d1-4a10e5f7bea7 and
timestamp: 2022-02-09T12:27:31.983000000Z:
Metric: Value:
dataflow_v2_java11_runtime_sec 7806.336
dataflow_v2_java11_total_bytes_count 6.8698877E9
Exception in thread "main" java.lang.RuntimeException: Invalid job state:
CANCELLED.
at
org.apache.beam.sdk.loadtests.JobFailure.handleFailure(JobFailure.java:51)
at org.apache.beam.sdk.loadtests.LoadTest.run(LoadTest.java:139)
at
org.apache.beam.sdk.loadtests.GroupByKeyLoadTest.run(GroupByKeyLoadTest.java:57)
at
org.apache.beam.sdk.loadtests.GroupByKeyLoadTest.main(GroupByKeyLoadTest.java:131)
> Task :sdks:java:testing:load-tests:run FAILED
> Task :runners:google-cloud-dataflow-java:cleanUpDockerJavaImages
Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220209122406
Untagged:
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:0eb32302091dfbc846eed26ce593c965050a87c968adc3d59a551e65c42731c9
Tag: [us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220209122406]
- referencing digest:
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:0eb32302091dfbc846eed26ce593c965050a87c968adc3d59a551e65c42731c9]
Deleted [[us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220209122406]
(referencing
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:0eb32302091dfbc846eed26ce593c965050a87c968adc3d59a551e65c42731c9])].
Removing untagged image
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:0eb32302091dfbc846eed26ce593c965050a87c968adc3d59a551e65c42731c9
Digests:
-
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:0eb32302091dfbc846eed26ce593c965050a87c968adc3d59a551e65c42731c9
Deleted
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:0eb32302091dfbc846eed26ce593c965050a87c968adc3d59a551e65c42731c9].
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':sdks:java:testing:load-tests:run'.
> Process 'command '/usr/lib/jvm/java-8-openjdk-amd64/bin/java'' 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.
> Run with --scan to get full insights.
* 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.3.2/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 3h 40m 31s
109 actionable tasks: 72 executed, 33 from cache, 4 up-to-date
Publishing build scan...
https://gradle.com/s/adeos6r7t6wde
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]
