[GitHub] [druid] bharadwajrembar commented on issue #9212: azure extensions: task log kill crashes with "Not Implemented".

[GitBox <gi...@apache.org>]

bharadwajrembar commented on issue #9212: azure extensions: task log kill crashes with "Not Implemented".
URL: https://github.com/apache/druid/issues/9212#issuecomment-606670244
 
 
   We are hit with the same for S3 on version `0.17.0`. @jihoonson We use the Router for our UI. When we go into the `Ingestion` tab, the API fires this SQL query:
   
   ```
   SELECT  "task_id", "group_id", "type", "datasource", "created_time", "location", "duration", "error_msg",  
   CASE WHEN "status" = 'RUNNING' THEN "runner_status" ELSE "status" END AS "status", 
    (    CASE WHEN "status" = 'RUNNING' THEN     (CASE "runner_status" WHEN 'RUNNING' THEN 4 WHEN 'PENDING' THEN 3 ELSE 2 END)    ELSE 1    END  ) 
    AS "rank"FROM sys.tasks ORDER BY "rank" DESC, "created_time" DESC
   ```
   and it takes sometime to load.
   
   Does this query go to the Overlord? If so, is having a large number of old tasks in the metadata likely to affect performance or even potentially cause OOMs in the Overlord?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org