If through impala-shell then you should see something like "Query progress can be monitored at: http://[coordinator_hostname]:25000/query_plan?query_id=984ed18511f4ae82:9ccc11c300000000 " and you could go there to see its progress. Or you can start impala-shell with --live_summary and see progress of each fragment in realtime.
If through odbc/jdbc, and you're specifying a node directly (not through haproxy), then you can go directly here for that node:
and see any queries running there, even if for some reason they're not coming up in CM.
Well if you can't access the impala UI on that node then you have bigger problems than that query. Perhaps your impalad is hung? or maybe you have a firewall or network policy that is not allowing you to access that port?
Could you first of all try restarting that impalad?
So this query hangs the daemon but other queries run fine? Oh wow that's strange, I would expect it to fail with out-of-memory error or something.
Do you have really low memory on the daemon, like under 16GB?
You should review the daemon INFO log under /var/log/impalad and search for the query id, see how it progresses and where it gets stuck (you can compare entries vs. another query that runs fine). You'll see a lot of info about fragments being setup and distributed.
It's stuck in a CREATED state (if I remember correctly at one time I could get to the daemon page), I don't remember about other queries cause when I've checked only this query was on the daemon and the daemon was page stuck in my browser.
My daemon has exactly 16GB.
Thanks, I'll try that, there any other tracing tool I can use to check the daemon or the query?