Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

web console: display index_parallel progress #8856

Open
glasser opened this issue Nov 11, 2019 · 2 comments
Open

web console: display index_parallel progress #8856

glasser opened this issue Nov 11, 2019 · 2 comments

Comments

@glasser
Copy link
Contributor

glasser commented Nov 11, 2019

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.

@vogievetsky
Copy link
Contributor

👍 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

@glasser
Copy link
Contributor Author

glasser commented Nov 12, 2019

That makes sense.

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.

(ps hope to meet you tonight!)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants