[GitHub] flink pull request #3229: [FLINK-5663] Prevent leaking SafetyNetCloseableReg...

2017-01-27 Thread StefanRRichter
GitHub user StefanRRichter opened a pull request:

https://github.com/apache/flink/pull/3229

[FLINK-5663] Prevent leaking SafetyNetCloseableRegistry through Inher…

This PR prevents the SafetyNetCloseableRegistry from leaking into pooled 
threads through InheritableThreadLocal.

As first step, we use ThreadLocal instead of InheritableThreadLocal to hold 
the closeable registries.

Additionally, we also create safety nets for the file system at the scope 
of the checkpointing thread. We hope that this covers already covers most 
cases. Other threads could actually also create safety nets for their scope 
right now.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/StefanRRichter/flink safetyNetThreadLocal

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/flink/pull/3229.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #3229


commit 31ae956fdd83a2f65bf22c3ad601d4d65ad61439
Author: Stefan Richter 
Date:   2017-01-27T18:47:12Z

[FLINK-5663] Prevent leaking SafetyNetCloseableRegistry through 
InheritableThreadLocal




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] flink pull request #3229: [FLINK-5663] Prevent leaking SafetyNetCloseableReg...

2017-01-29 Thread asfgit
Github user asfgit closed the pull request at:

https://github.com/apache/flink/pull/3229


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---