You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@flink.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/04/06 07:08:00 UTC
[jira] [Updated] (FLINK-27070) Reuse FileFormat instead of DecodingFormat/EncodingFormat to ensure thread safety.
[ https://issues.apache.org/jira/browse/FLINK-27070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
ASF GitHub Bot updated FLINK-27070:
-----------------------------------
Labels: pull-request-available (was: )
> Reuse FileFormat instead of DecodingFormat/EncodingFormat to ensure thread safety.
> ----------------------------------------------------------------------------------
>
> Key: FLINK-27070
> URL: https://issues.apache.org/jira/browse/FLINK-27070
> Project: Flink
> Issue Type: Sub-task
> Components: Table Store
> Affects Versions: 0.1.0
> Reporter: Caizhi Weng
> Priority: Major
> Labels: pull-request-available
> Fix For: 0.1.0
>
>
> When testing table store I'm faced with the following warning messages:
> {code}
> org.apache.org.impl.MemoryManagerImpl [] - Owner thread expected Thread[Writer -> Local Committer (1/16)#0,5,Flink Task Threads], got Thread[pool-8-thread-1,5,Flink Task Threads]
> {code}
> This is because {{OrcBulkWriterFactory}} is not thread safe (it keeps {{WriterOptions}} as a class member and creates writers from the same {{WriterOptions}} object, which is not thread safe).
> What we should do is to reuse {{FileFormat}} instead of {{DecodingFormat}}/{{EncodingFormat}} to ensure thread safety.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)