GitHub user markap14 opened a pull request:
https://github.com/apache/nifi/pull/848
NIFI-2551: Addressed a threading issue in the
StandardResourceClaimManagerâ¦
⦠and performed some refactoring so that we can ensure thread-safety
across different components of the application, such as ProcessSession and
WriteAheadFlowFile Repository when interacting with the
StandardResourceClaimManager. Update DebugFlow to allow it to write to a
FlowFile multiple times, which exposes the concurrency bug. Also avoided
calling ContentRepository.remove() from ProcessSession whenever the content is
no longer needed, as that can cause problems now that the Resource Claim is
backing the content claim.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/markap14/nifi NIFI-2551-1.x
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/848.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 #848
----
commit 2c2b4e9a5ddf030b60631f8ef24fca3b8b5324d6
Author: Mark Payne <[email protected]>
Date: 2016-08-12T17:56:03Z
NIFI-2551: Addressed a threading issue in the StandardResourceClaimManager
and performed some refactoring so that we can ensure thread-safety across
different components of the application, such as ProcessSession and
WriteAheadFlowFile Repository when interacting with the
StandardResourceClaimManager. Update DebugFlow to allow it to write to a
FlowFile multiple times, which exposes the concurrency bug. Also avoided
calling ContentRepository.remove() from ProcessSession whenever the content is
no longer needed, as that can cause problems now that the Resource Claim is
backing the content claim.
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
