[
https://issues.apache.org/jira/browse/FLINK-14963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Flink Jira Bot updated FLINK-14963:
-----------------------------------
Labels: auto-deprioritized-major stale-minor (was:
auto-deprioritized-major)
I am the [Flink Jira Bot|https://github.com/apache/flink-jira-bot/] and I help
the community manage its development. I see this issues has been marked as
Minor but is unassigned and neither itself nor its Sub-Tasks have been updated
for 180 days. I have gone ahead and marked it "stale-minor". If this ticket is
still Minor, please either assign yourself or give an update. Afterwards,
please remove the label or in 7 days the issue will be deprioritized.
> Massive Duplicated Useless Oss Message in jobmanager.log
> --------------------------------------------------------
>
> Key: FLINK-14963
> URL: https://issues.apache.org/jira/browse/FLINK-14963
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / FileSystem
> Affects Versions: 1.9.1
> Reporter: Eric Lee
> Priority: Minor
> Labels: auto-deprioritized-major, stale-minor
> Attachments: 7120B204-1B34-46D5-A9ED-D5BAB2D76F26.png
>
>
> When I was using AliCloud Oss as the external file system for flink
> checkpoints, there were massive oss related logs which are useless because
> checkpoints can still complete successfully.
> After I debugged into checkpoint coordinator and file system, I found the
> root cause, the wrong use of oss sdk to check whether the target exists in
> hadoop fs module.
> (Attached image is the screenshot of jobmanager.log)
> ----
> Solutions:
> I have submitted a [pull request
> |https://github.com/aliyun/aliyun-oss-java-sdk/pull/264]in aliyun-oss-client
> repository and v3.8.0 has released. We can alter the oss client version with
> [3.8.0|https://github.com/apache/flink/blob/master/flink-filesystems/flink-oss-fs-hadoop/pom.xml#L31].
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
