You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@drill.apache.org by "Abhishek Girish (JIRA)" <ji...@apache.org> on 2015/05/18 05:43:59 UTC
[jira] [Updated] (DRILL-3125) Drill UI Profile page fails to load
for a query in some scenarios
[ https://issues.apache.org/jira/browse/DRILL-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Abhishek Girish updated DRILL-3125:
-----------------------------------
Description:
- Start a long running query via Sqlline / Drill UI
- Look for the query on the Profile page on Drill UI
Opening the query's profile fails:
{code}
HTTP ERROR 500
Problem accessing /profiles/2aa6a139-95c3-a30b-bc66-b33491b0d619. Reason:
Request failed.
Powered by Jetty://
{code}
This usually happens for me when the query is running on Node 1 as Foreman and Drill UI is on Node 2.
was:
- Start a long running query via Sqlline / Drill UI
- Look for the query on the Profile page on Drill UI
Opening the query's profile fails:
{code}
HTTP ERROR 500
Problem accessing /profiles/2aa6a139-95c3-a30b-bc66-b33491b0d619. Reason:
Request failed.
Powered by Jetty://
{code}
> Drill UI Profile page fails to load for a query in some scenarios
> -----------------------------------------------------------------
>
> Key: DRILL-3125
> URL: https://issues.apache.org/jira/browse/DRILL-3125
> Project: Apache Drill
> Issue Type: Bug
> Components: Client - HTTP
> Affects Versions: 1.0.0
> Reporter: Abhishek Girish
> Assignee: Jason Altekruse
>
> - Start a long running query via Sqlline / Drill UI
> - Look for the query on the Profile page on Drill UI
> Opening the query's profile fails:
> {code}
> HTTP ERROR 500
> Problem accessing /profiles/2aa6a139-95c3-a30b-bc66-b33491b0d619. Reason:
> Request failed.
> Powered by Jetty://
> {code}
> This usually happens for me when the query is running on Node 1 as Foreman and Drill UI is on Node 2.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)