drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Rogers (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DRILL-5156) Bit-Client thread finds closed allocator in TestDrillbitResilience unit test
Date Fri, 23 Dec 2016 03:29:58 GMT
Paul Rogers created DRILL-5156:

             Summary: Bit-Client thread finds closed allocator in TestDrillbitResilience unit
                 Key: DRILL-5156
                 URL: https://issues.apache.org/jira/browse/DRILL-5156
             Project: Apache Drill
          Issue Type: Bug
            Reporter: Paul Rogers
            Priority: Minor

RPC thread attempts to access a closed allocator during the {{TestDrillbitResilience}} unit

Set a Java exception breakpoint for {{IllegalStateException}}. Run the {{TestDrillbitResilience}}
unit tests.

You will see quite a few exceptions, including the following in a thread called BitClient-1:

RootAllocator(BaseAllocator).assertOpen() line 109
RootAllocator(BaseAllocator).buffer(int) line 191
DrillByteBufAllocator.buffer(int) line 49
DrillByteBufAllocator.ioBuffer(int) line 64
AdaptiveRecvByteBufAllocatpr$HandleImpl.allocate(ByteBufAllocator) line 104
NioSocketChannel$NioSocketChannelUnsafe(...).read() line 117
NioEventLoop.run() line 354

The test continues (then fails for some other reason), which is why this is marked as minor.
Still, it seems odd that the client thread should attempt to access a closed allocator.

At this point, it is not clear how we got into this state. The test itself is waiting for
a response from the server in the {{tailsAfterMSorterSorting}} test.

This message was sent by Atlassian JIRA

View raw message