[ 
https://issues.apache.org/jira/browse/FLINK-40123?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18131068#comment-18131068
 ] 

Martijn Visser commented on FLINK-40123:
----------------------------------------

Thanks, that matches the 3.3.4 source: BlockUploadProgress is a plain SDK v1 
ProgressListener, so the byte-transfer event lands on the SDK callback thread 
after putObject() has returned. I'd go with option 1, an entry next to 
'INFO.*AWSErrorCode' in default_allowed_exceptions matching S3AInstrumentation 
plus the message text. test_file_sink.sh and test_batch_wordcount.sh write 
through the same plugin, so a per-test list would only cover one of three, and 
changing the log level touches the shared conf. It needs to go to release-2.2 
and release-2.3 as well, both still on Hadoop 3.3.4. Do you want to open the PR?

> heck_logs_for_exceptions false-positives on S3A stream_write_exceptions 
> counter, flaking test_kubernetes_materialized_table.sh
> ------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: FLINK-40123
>                 URL: https://issues.apache.org/jira/browse/FLINK-40123
>             Project: Flink
>          Issue Type: Improvement
>    Affects Versions: 2.2.2, 2.3.1, 2.4.0
>         Environment: Azure build 76427, task "Run e2e tests" (log 87).
>  
> https://dev.azure.com/apache-flink/98463496-1af2-4620-8eab-a2ecc1a2e6fe/_build/results?buildId=76427
>            Reporter: Shekhar Prasad Rajak
>            Priority: Major
>             Fix For: 2.3.1
>
>
> The e2e test Run kubernetes Materialized Table test 
> (flink-end-to-end-tests/test-scripts/test_kubernetes_materialized_table.sh) 
> intermittently fails even though the test logic itself
>   succeeds:
>   [FAIL] 'Run kubernetes Materialized Table test' failed after 4 minutes and 
> 20 seconds!
>   Test exited with exit code 0 but the logs contained errors, exceptions or 
> non-empty .out files
>   Note exit code 0 — the test passed; the failure is raised entirely by the 
> post-run log scan.
>  
> How to reproduce
>   Run test_kubernetes_materialized_table.sh against a SeaweedFS/S3A-backed 
> catalog store; whenever the S3AInstrumentation "Closing output stream 
> statistics" WARN is logged, the run fails in
>   the exception check.



--
This message was sent by Atlassian Jira
(v10.3.26#10030026)

Reply via email to