Mailing-List: contact dev-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 8.2 \(2104\))
Subject: Re: Channel closed exception
From: Sudheesh Katkam <skatkam@maprtech.com>
In-Reply-To: <0258662709eb4f50b76d5eccf3db13b0@POST-4.gp.cv.commvault.com>
Date: Wed, 30 Sep 2015 20:54:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <B3FFF994-4B86-4106-B575-CA828DED25D8@maprtech.com>
References: <491ad122ca864a0695a89b91e579be53@POST-4.gp.cv.commvault.com>
 <7830774A-1C8C-4E03-8735-18BAD717876A@maprtech.com>
 <0258662709eb4f50b76d5eccf3db13b0@POST-4.gp.cv.commvault.com>
To: dev@drill.apache.org

Are you running drill in embedded mode? The directory containing the =
drillbit.log file contains the drillbit.out file too. There might be a =
JVM core dump in the /tmp directory.

Usually "Received shutdown request=E2=80=9D message means that=E2=80=99s =
the drillbit ran out of memory. Given that you mentioned the query is on =
a large document set, this scenario is likely.

- Sudheesh

> On Sep 30, 2015, at 8:46 PM, Sudip Mukherjee =
<smukherjee@commvault.com> wrote:
>=20
> Hi,
> This is the excerpt of exception in sqlline.log. Could you please =
refer me to the location of drillbit.out file?
>=20
>=20
> 2015-09-30 22:23:36,286 [BitServer-4] WARN  =
o.a.d.exec.rpc.control.ControlServer - Message of mode REQUEST of rpc =
type 6 took longer than 500ms.  Actual duration was 16047ms.
> 2015-09-30 22:24:13,581 =
[29f36725-9de3-b370-7f38-50ebbe677bf7:frag:0:0] INFO  =
o.a.d.e.w.fragment.FragmentExecutor - =
29f36725-9de3-b370-7f38-50ebbe677bf7:0:0: State change requested =
CANCELLATION_REQUESTED --> FINISHED
> 2015-09-30 22:24:13,581 =
[29f36725-9de3-b370-7f38-50ebbe677bf7:frag:0:0] INFO  =
o.a.d.e.w.f.FragmentStatusReporter - =
29f36725-9de3-b370-7f38-50ebbe677bf7:0:0: State to report: CANCELLED
> 2015-09-30 22:24:13,581 [BitServer-4] INFO  =
o.a.drill.exec.work.foreman.Foreman - State change requested.  =
CANCELLATION_REQUESTED --> COMPLETED
> 2015-09-30 22:24:13,581 [BitServer-4] INFO  =
o.a.drill.exec.work.foreman.Foreman - foreman cleaning up.
> 2015-09-30 22:24:13,597 [UserServer-1] INFO  =
o.a.drill.exec.work.foreman.Foreman - Failure while trying communicate =
query result to initiating client. This would happen if a client is =
disconnected before response notice can be sent.
> org.apache.drill.exec.rpc.ChannelClosedException: null
> 	at =
org.apache.drill.exec.rpc.CoordinationQueue$RpcListener.operationComplete(=
CoordinationQueue.java:89) =
[drill-java-exec-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
> 	at =
org.apache.drill.exec.rpc.CoordinationQueue$RpcListener.operationComplete(=
CoordinationQueue.java:67) =
[drill-java-exec-1.2.0-SNAPSHOT.jar:1.2.0-SNAPSHOT]
> 	at =
io.netty.util.concurrent.DefaultPromise.notifyListener0(DefaultPromise.jav=
a:680) [netty-common-4.0.27.Final.jar:4.0.27.Final]
> 	at =
io.netty.util.concurrent.DefaultPromise.notifyListeners0(DefaultPromise.ja=
va:603) [netty-common-4.0.27.Final.jar:4.0.27.Final]
> 	at =
io.netty.util.concurrent.DefaultPromise.notifyListeners(DefaultPromise.jav=
a:563) [netty-common-4.0.27.Final.jar:4.0.27.Final]
> 	at =
io.netty.util.concurrent.DefaultPromise.tryFailure(DefaultPromise.java:424=
) [netty-common-4.0.27.Final.jar:4.0.27.Final]
>=20
> Thanks,
> Sudip
>=20
> -----Original Message-----
> From: Sudheesh Katkam [mailto:skatkam@maprtech.com]=20
> Sent: 01 October 2015 AM 09:09
> To: dev@drill.apache.org
> Subject: Re: Channel closed exception
>=20
> Can you check if there are any error messages in the drillbit.out =
file?
>=20
> - Sudheesh
>=20
>> On Sep 30, 2015, at 8:35 PM, Sudip Mukherjee =
<smukherjee@commvault.com> wrote:
>>=20
>> Hi Devs,
>>=20
>> Getting into a channel closed exception when I tried to connect drill =
to tableau and query a large document set. Could it be because tableau =
dropped the connection due to datasize. Any thoughts?
>>=20
>> 2015-09-30 21:13:43,716=20
>> [29f3777a-d407-295a-d45e-243fb70efc07:frag:0:0] INFO =20
>> o.a.d.e.w.fragment.FragmentExecutor -=20
>> 29f3777a-d407-295a-d45e-243fb70efc07:0:0: State change requested=20
>> AWAITING_ALLOCATION --> RUNNING
>> 2015-09-30 21:13:43,716=20
>> [29f3777a-d407-295a-d45e-243fb70efc07:frag:0:0] INFO =20
>> o.a.d.e.w.f.FragmentStatusReporter -=20
>> 29f3777a-d407-295a-d45e-243fb70efc07:0:0: State to report: RUNNING
>> 2015-09-30 21:14:36,875=20
>> [29f3777a-d407-295a-d45e-243fb70efc07:frag:0:0] INFO =20
>> o.a.d.e.w.fragment.FragmentExecutor -=20
>> 29f3777a-d407-295a-d45e-243fb70efc07:0:0: State change requested=20
>> RUNNING --> FINISHED
>> 2015-09-30 21:14:36,876=20
>> [29f3777a-d407-295a-d45e-243fb70efc07:frag:0:0] INFO =20
>> o.a.d.e.w.f.FragmentStatusReporter -=20
>> 29f3777a-d407-295a-d45e-243fb70efc07:0:0: State to report: FINISHED
>> 2015-09-30 21:14:36,877 [BitServer-4] INFO =20
>> o.a.drill.exec.work.foreman.Foreman - State change requested.  =
RUNNING=20
>> --> COMPLETED
>> 2015-09-30 21:14:36,877 [BitServer-4] INFO  =
o.a.drill.exec.work.foreman.Foreman - foreman cleaning up.
>> 2015-09-30 21:33:09,745 [Client-1] INFO  =
o.a.drill.exec.rpc.user.UserClient - Channel closed /172.19.77.101:57162 =
<--> DEVSTAGING2.testlab.commvault.com/172.19.77.101:31010.
>> 2015-09-30 21:33:12,859 [BitServer-3] INFO  =
o.a.d.exec.rpc.control.ControlClient - Channel closed =
/172.19.77.101:57207 <--> =
DEVSTAGING2.testlab.commvault.com/172.19.77.101:31011.
>> 2015-09-30 21:33:16,077 [main] INFO  =
o.apache.drill.exec.server.Drillbit - Shutdown completed (6331 ms).
>> 2015-09-30 21:33:16,102 [Drillbit-ShutdownHook#0] INFO  =
o.apache.drill.exec.server.Drillbit - Received shutdown request.
>>=20
>> Thanks,
>> Sudip
>>=20
>>=20
>>=20
>> ***************************Legal =
Disclaimer***************************
>> "This communication may contain confidential and privileged material=20=

>> for the sole use of the intended recipient. Any unauthorized review,=20=

>> use or distribution by others is strictly prohibited. If you have=20
>> received the message by mistake, please advise the sender by reply =
email and delete the message. Thank you."
>> =
**********************************************************************
>=20
>=20
>=20
>=20
>=20
> ***************************Legal Disclaimer***************************
> "This communication may contain confidential and privileged material =
for the
> sole use of the intended recipient. Any unauthorized review, use or =
distribution
> by others is strictly prohibited. If you have received the message by =
mistake,
> please advise the sender by reply email and delete the message. Thank =
you."
> **********************************************************************