[jira] [Commented] (KUDU-1748) /inflight_query_ids returns "\n" when no queries are running

["Todd Lipcon (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/KUDU-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15669198#comment-15669198 ] 

Todd Lipcon commented on KUDU-1748:
-----------------------------------

This seems like an Impala bug, rather than a Kudu one, and not a Kudu-specific Impala issue. I am pretty sure they've already fixed this in current builds.

> /inflight_query_ids returns "\n" when no queries are running
> ------------------------------------------------------------
>
>                 Key: KUDU-1748
>                 URL: https://issues.apache.org/jira/browse/KUDU-1748
>             Project: Kudu
>          Issue Type: Bug
>          Components: impala
>    Affects Versions: 1.0.0
>            Reporter: Shravan Pabba
>
> Cloudera Manager Query Monitoring Status Check Keeps failing for all the impala daemons for Impala_kudu service.
> Cloudera support team did the analysis and here is more information,
> From the collected tcpdump, we see that the result returned by Impala daemon for the "inflight_query_ids" check made by cloudera-scm-agent is of length 1 character.
> ---------------------------
> GET /inflight_query_ids HTTP/1.1
> Accept-Encoding: identity
> Host: ebdp-avdc-d324p.sys.comcast.net:25000
> Connection: close
> User-Agent: Python-urllib/2.6
> HTTP/1.1 200 OK
> Content-Type: text/plain
> Content-Length: 1
> X-Frame-Options: DENY
> ---------------------------
> Hence 'inflight_query_ids' web call is returning '\n' if there are no queries in flight (as visible from capture), instead of the expected empty string. This causes Cloudera Manager agent query monitor call to fail.
> -------------------
> Could not obtain runtime profile: Query id 0:0 not found.
> -----------------
> Need the inflight_query_ids to return empty string instead of "\n"



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