GitHub user jacques-n opened a pull request:
https://github.com/apache/drill/pull/323
DRILL-4246: Fix Allocator concurrency bug and improve error detection
- Rename the internal DrillBuf field to udle to better express its purpose.
- Rename AllocatorManager to AllocationManager to better express its
purpose.
- Address situation where dangling ledger could be transferred into while
it was being released released by protecting association and release inside the
AllocationManager.
- Add allocator assertions to ensure allocator operations are done while
the allocator is open.
- Simplify AllocationManager locking model.
- Exclude HDFS reference to netty-all
- Improve debugging messages for allocators (and fix debug message bugs)
Tests pending but evaluation shows previously frequently failing flatten
tests to consistently pass.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jacques-n/drill DRILL-4246
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/drill/pull/323.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 #323
----
commit 4b193d71a9f3e06aadf59c66832bcbcb4b060c92
Author: Jacques Nadeau <[email protected]>
Date: 2016-01-11T04:08:03Z
DRILL-4246: Fix Allocator concurrency bug and improve error detection
- Rename the internal DrillBuf field to udle to better express its purpose.
- Rename AllocatorManager to AllocationManager to better express its
purpose.
- Address situation where dangling ledger could be transferred into while
it was being released released by protecting association and release inside the
AllocationManager.
- Add allocator assertions to ensure allocator operations are done while
the allocator is open.
- Simplify AllocationManager locking model.
- Exclude HDFS reference to netty-all
- Improve debugging messages for allocators (and fix debug message bugs)
----
---
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.
---
