You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Native batch ingestion exposes progress stats for its subtasks (number of succeeded/running/total/etc tasks) on the http://{PEON_IP}:{PEON_PORT}/druid/worker/v1/chat/{SUPERVISOR_TASK_ID}/progress endpoint.
It would be great if this were visible somewhere while examining an index_parallel task in the web console, either somewhere in the popup revealed by the magnifying glass icon, or even in a column in the task list as a progress bar.
It might be a good idea to proxy this task through another server (overlord?) because peon hostnames might not be resolvable from a user's browser.
The text was updated successfully, but these errors were encountered:
👍 the only reason that it is not there is because there is no mechanism for the console, which is served from the Router (and soon coordinator + overlord, shoutout to #8838), to talk to the peon APIs
We would need to have some sort of proxy. Shoutout to #8686
My understanding is that the "reports" concept which isn't currently used by index_parallel tasks is an end-of-task-only thing and can't be used for progress, right?
Another alternative would be a way to get things like progress into the overlord's understanding of task status.
Native batch ingestion exposes progress stats for its subtasks (number of succeeded/running/total/etc tasks) on the
http://{PEON_IP}:{PEON_PORT}/druid/worker/v1/chat/{SUPERVISOR_TASK_ID}/progress
endpoint.It would be great if this were visible somewhere while examining an index_parallel task in the web console, either somewhere in the popup revealed by the magnifying glass icon, or even in a column in the task list as a progress bar.
It might be a good idea to proxy this task through another server (overlord?) because peon hostnames might not be resolvable from a user's browser.
The text was updated successfully, but these errors were encountered: