See 
<https://ci-beam.apache.org/job/beam_LoadTests_Java_GBK_Dataflow_V2_Streaming_Java11/201/display/redirect?page=changes>

Changes:

[mmack] [BEAM-13509] Stop sharing SQS client between readers of same source.

[mmack] [BEAM-13587] Attempt to load AWS region from default provider chain in


------------------------------------------
[...truncated 68.75 KB...]
INFO: 2022-01-04T14:27:41.628Z: 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.
Jan 04, 2022 2:31:46 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:31:45.758Z: 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.
Jan 04, 2022 2:35:46 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:35:44.301Z: 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.
Jan 04, 2022 2:36:48 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:36:47.805Z: 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.
Jan 04, 2022 2:38:53 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:38:50.947Z: 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.
Jan 04, 2022 2:39:52 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:39:51.442Z: 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.
Jan 04, 2022 2:41:54 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:41:54.646Z: 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.
Jan 04, 2022 2:44:59 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:44:58.736Z: 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.
Jan 04, 2022 2:47:57 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:47:57.475Z: 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.
Jan 04, 2022 2:49:03 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:49:02.705Z: 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.
Jan 04, 2022 2:50:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:50:01.588Z: 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.
Jan 04, 2022 2:53:10 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:53:08.585Z: 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.
Jan 04, 2022 2:54:07 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:54:06.696Z: 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.
Jan 04, 2022 2:57:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:57:12.424Z: 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.
Jan 04, 2022 2:58:11 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T14:58:11.031Z: 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.
Jan 04, 2022 3:00:15 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:00:14.442Z: 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.
Jan 04, 2022 3:01:19 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:01:17.878Z: 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.
Jan 04, 2022 3:03:18 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:03:17.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.
Jan 04, 2022 3:05:23 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:05:22.726Z: 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.
Jan 04, 2022 3:08:23 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:08:23.052Z: 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.
Jan 04, 2022 3:09:29 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:09:28.303Z: 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.
Jan 04, 2022 3:11:28 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:11:26.642Z: 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.
Jan 04, 2022 3:13:30 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:13:30.191Z: 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.
Jan 04, 2022 3:14:35 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:14:33.652Z: 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.
Jan 04, 2022 3:22:35 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:22:34.412Z: 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.
Jan 04, 2022 3:23:39 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:23:37.995Z: 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.
Jan 04, 2022 3:24:42 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:24:41.487Z: 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.
Jan 04, 2022 3:26:48 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:26:46.676Z: 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.
Jan 04, 2022 3:30:45 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:30:45.405Z: 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.
Jan 04, 2022 3:34:51 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:34:50.860Z: 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.
Jan 04, 2022 3:35:49 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:35:49.815Z: 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.
Jan 04, 2022 3:36:54 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:36:53.430Z: 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.
Jan 04, 2022 3:40:33 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
SEVERE: 2022-01-04T15:40:30.463Z: generic::aborted: SDK harness sdk-0-0 
disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
generic::aborted: SDK harness sdk-0-0 disconnected.
generic::aborted: SDK harness sdk-0-0 disconnected.
passed through:
==>
    dist_proc/dax/workflow/****/fnapi_service_impl.cc:771
Jan 04, 2022 3:41:54 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:41:53.917Z: 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.
Jan 04, 2022 3:43:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:42:58.855Z: 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.
Jan 04, 2022 3:44:00 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:43:58.565Z: 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.
Jan 04, 2022 3:47:02 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:47:02.540Z: 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.
Jan 04, 2022 3:50:06 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:50:04.702Z: 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.
Jan 04, 2022 3:51:10 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:51:09.922Z: 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.
Jan 04, 2022 3:54:10 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:54:09.865Z: 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.
Jan 04, 2022 3:55:13 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T15:55:12.589Z: 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.
Jan 04, 2022 4:00:35 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T16:00:35.248Z: Cancel request is committed for workflow job: 
2022-01-04_04_10_14-16753803227630158619.
Jan 04, 2022 4:00:35 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T16:00:35.283Z: Cleaning up.
Jan 04, 2022 4:00:35 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T16:00:35.360Z: Stopping **** pool...
Jan 04, 2022 4:00:35 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T16:00:35.420Z: Stopping **** pool...
Jan 04, 2022 4:03:26 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T16:03:26.782Z: 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.
Jan 04, 2022 4:03:26 PM 
org.apache.beam.runners.dataflow.util.MonitoringUtil$LoggingHandler process
INFO: 2022-01-04T16:03:26.819Z: Worker pool stopped.
Jan 04, 2022 4:03:32 PM org.apache.beam.runners.dataflow.DataflowPipelineJob 
logTerminalState
INFO: Job 2022-01-04_04_10_14-16753803227630158619 finished with status 
CANCELLED.
Load test results for test (ID): ff3666ac-bada-4247-a342-5b03f72b4c4a and 
timestamp: 2022-01-04T12:10:08.593000000Z:
                 Metric:                    Value:
dataflow_v2_java11_runtime_sec                 13165.372
dataflow_v2_java11_total_bytes_count              6.14054294E9
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:cleanUpDockerImages
Untagged: us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220104120618
Untagged: 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:aaac42355cb319daab1b959ab0d8b9db50dab1e69bb3c00cc3b786ae64d88f1b
Tag: [us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220104120618]
- referencing digest: 
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:aaac42355cb319daab1b959ab0d8b9db50dab1e69bb3c00cc3b786ae64d88f1b]

Deleted [[us.gcr.io/apache-beam-testing/java-postcommit-it/java:20220104120618] 
(referencing 
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:aaac42355cb319daab1b959ab0d8b9db50dab1e69bb3c00cc3b786ae64d88f1b])].
Removing untagged image 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:aaac42355cb319daab1b959ab0d8b9db50dab1e69bb3c00cc3b786ae64d88f1b
Digests:
- 
us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:aaac42355cb319daab1b959ab0d8b9db50dab1e69bb3c00cc3b786ae64d88f1b
Deleted 
[us.gcr.io/apache-beam-testing/java-postcommit-it/java@sha256:aaac42355cb319daab1b959ab0d8b9db50dab1e69bb3c00cc3b786ae64d88f1b].

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 57m 33s
89 actionable tasks: 52 executed, 33 from cache, 4 up-to-date

Publishing build scan...
https://gradle.com/s/npran5b2zekvc

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]

Reply via email to