Hi Jing,
I agree that in this version it's not really convenient to check out if
there are
speculative attempts. I think what we need to improve this is not only the
enhancement of the current Web UI, but a new page summarizing the
information of speculative execution on the history server, or bot
Hi Gen,
> The way the speculative executions are presented should be almost the
same as the
job was running. Users can still find the executions folded in the subtask
list page.
It's a more complicated operation to check all vertex and all subtasks list
page.
It's better to have an easier way to
Hi Jing,
Thanks for joining the discussion. It's a very good point to figure out the
possible influence on the history server.
> 1. Does the improvement also cover history server or just Web UI?
As far as I know most Web UI components are shared between
runtime and history server, so the improvem
Thanks for driving this discussion. It's a very helpful improvement.
I only have two minor questions:
1. Does the improvement also cover history server or just Web UI?
2. How to know whether the job contains speculative execution instances
after the job finished?
Do we have to check each subtasks o
Hi, everyone.
Thanks for your feedback.
If there are no more concerns or comments, I will start the vote tomorrow.
Gen Luo 于 2022年7月11日周一 11:12写道：
> Hi Lijie and Zhu,
>
> Thanks for the suggestion. I agree that the name "Blocked Free Slots" is
> more clear to users.
> I'll take the suggestion a
Hi Lijie and Zhu,
Thanks for the suggestion. I agree that the name "Blocked Free Slots" is
more clear to users.
I'll take the suggestion and update the FLIP.
On Fri, Jul 8, 2022 at 9:12 PM Zhu Zhu wrote:
> I agree that it can be more useful to show the number of slots that are
> free but blocke
I agree that it can be more useful to show the number of slots that are
free but blocked. Currently users infer the slots in use by subtracting
available slots from the total slots. With blocked slots introduced, this
can be achieved by subtracting available slots and blocked free slots
from the to
Hi Gen & Zhu,
-> 1. Can we also show "Blocked Slots" in the resource card, so that users
can easily figure out how many slots are available/blocked/in-use?
I think we should describe the "available" and "blocked" more clearly. In
my opinion, I think users should be interested in the number of slo
Hi Zhu,
Thanks for the feedback!
1.Good idea. Users should be more familiar with the slots as the resource
units.
2.You remind me that the "speculative attempts" are execution attempts
started by the SpeculativeScheduler when slot tasks are detected, while the
current execution attempts other tha
Thanks for writing this FLIP and initiating the discussion, Gen, Yun and Junhan!
It will be very useful to have these improvements on the web UI for
speculative execution users, allowing them to know what is happening.
I just have a few comment regarding the design details:
1. Can we also show "Bl
Hi everyone,
The speculative execution for batch jobs has been proposed and accepted in
FLIP-168[1], as well as the related blocklist mechanism in FLIP-224[2]. As
a follow-up step, the Flink Web UI needs to be enhanced to display the
related information if the speculative execution mechanism is en
11 matches
Mail list logo
