drill-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Abhishek Girish (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (DRILL-3112) Drill UI profile page shows exceptions where a long running query is submitted via the UI
Date Fri, 15 May 2015 23:18:00 GMT

     [ https://issues.apache.org/jira/browse/DRILL-3112?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Abhishek Girish resolved DRILL-3112.
------------------------------------
    Resolution: Invalid

I think the UI was slow to load and displayed the contents of the thread page instead. Its
still a usability issue, but closing for now. 

> Drill UI profile page shows exceptions where a long running query is submitted via the
UI
> -----------------------------------------------------------------------------------------
>
>                 Key: DRILL-3112
>                 URL: https://issues.apache.org/jira/browse/DRILL-3112
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - HTTP
>    Affects Versions: 1.0.0
>            Reporter: Abhishek Girish
>            Assignee: Jason Altekruse
>
> When a long running query is being executed via Drill UI Query tab, clicking on the Profiles
tab throws exceptions:
> {code}
> Reference Handler id=2 state=WAITING
>     - waiting on <0x07670f3b> (a java.lang.ref.Reference$Lock)
>     - locked <0x07670f3b> (a java.lang.ref.Reference$Lock)
>     at java.lang.Object.wait(Native Method)
>     at java.lang.Object.wait(Object.java:503)
>     at java.lang.ref.Reference$ReferenceHandler.run(Reference.java:133)
> Finalizer id=3 state=WAITING
>     - waiting on <0x5ddbc511> (a java.lang.ref.ReferenceQueue$Lock)
>     - locked <0x5ddbc511> (a java.lang.ref.ReferenceQueue$Lock)
>     at java.lang.Object.wait(Native Method)
>     at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:135)
>     at java.lang.ref.ReferenceQueue.remove(ReferenceQueue.java:151)
>     at java.lang.ref.Finalizer$FinalizerThread.run(Finalizer.java:209)
> Signal Dispatcher id=5 state=RUNNABLE
> ConnectionStateManager-0 id=32 state=WAITING
>     - waiting on <0x566e36fb> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
>     - locked <0x566e36fb> (a java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject)
>     at sun.misc.Unsafe.park(Native Method)
>     at java.util.concurrent.locks.LockSupport.park(LockSupport.java:186)
>     at java.util.concurrent.locks.AbstractQueuedSynchronizer$ConditionObject.await(AbstractQueuedSynchronizer.java:2043)
>     at java.util.concurrent.ArrayBlockingQueue.take(ArrayBlockingQueue.java:374)
>     at org.apache.curator.framework.state.ConnectionStateManager.processEvents(ConnectionStateManager.java:208)
>     at org.apache.curator.framework.state.ConnectionStateManager.access$000(ConnectionStateManager.java:42)
>     at org.apache.curator.framework.state.ConnectionStateManager$1.call(ConnectionStateManager.java:110)
>     at java.util.concurrent.FutureTask.run(FutureTask.java:262)
>     at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
>     at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
>     at java.lang.Thread.run(Thread.java:745)
>     Locked synchronizers: count = 1
>       - java.util.concurrent.ThreadPoolExecutor$Worker@7468776f
> ...
> ...
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message