[
https://issues.apache.org/jira/browse/FLINK-5696?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15851278#comment-15851278
]
Stephan Ewen commented on FLINK-5696:
-------------------------------------
I think this is not a problem. As long as the registry is alive, the reaper
thread cannot have been shut down and replaced. That is a result of the atomic
reference count maintained by the constructor and {{close()}} method.
> Access to REAPER_THREAD lacks proper synchronization in
> SafetyNetCloseableRegistry#doRegister
> ---------------------------------------------------------------------------------------------
>
> Key: FLINK-5696
> URL: https://issues.apache.org/jira/browse/FLINK-5696
> Project: Flink
> Issue Type: Bug
> Reporter: Ted Yu
>
> Here is related code:
> {code}
> PhantomDelegatingCloseableRef phantomRef = new
> PhantomDelegatingCloseableRef(
> wrappingProxyCloseable,
> this,
> REAPER_THREAD.referenceQueue);
> {code}
> Access to REAPER_THREAD should be guarded by REAPER_THREAD_LOCK
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
