Hello @Malrashed,
We’ll need a few additional details before we can advise further.
From your description, it sounds like the delay occurs only when submitting queries via Hue — specifically, the query takes a while to appear in the Queries tab — while running the same query through impala-shell works as expected. Could you confirm if that’s correct?
If so, do you recall any recent changes made to the cluster before this issue began?
If the delay is limited to Hue, we should check whether it’s a Hue-side latency. In the Hue logs (rungunicorn.log), look for the time difference between:
'ImpalaService.ImpalaHiveServer2Service.Client'>.ExecuteStatement
and
'ImpalaService.ImpalaHiveServer2Service.Client'>.FetchResults
Make sure you match the same guid in both lines so we’re looking at the request/response for the same session. This will help us determine whether the delay is in Hue or elsewhere in the query path.
If you don’t see any delay in Hue, check the agent and Service Monitor logs (cloudera-scm-firehose) to make sure there’s no lag in processing JMX data. Also, verify the CM server logs to make sure there is no GC pauses.
If those logs look clean (no errors or heap issues), try adjusting the polling interval in Cloudera Manager:
CM > Impala > Configuration > query_monitoring_period_seconds
