-
Notifications
You must be signed in to change notification settings - Fork 13.5k
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
[FLINK-17130][web] Enable listing JM Logs and displaying Logs by filename #11731
Conversation
Thanks a lot for your contribution to the Apache Flink project. I'm the @flinkbot. I help the community Automated ChecksLast check on commit 2a9f46b (Tue Apr 14 09:34:38 UTC 2020) Warnings:
Mention the bot in a comment to re-run the automated checks. Review Progress
Please see the Pull Request Review Guide for a full explanation of the review process. The Bot is tracking the review progress through labels. Labels are applied according to the order of the review items. For consensus, approval by a Flink committer of PMC member is required Bot commandsThe @flinkbot bot supports the following commands:
|
@simplejason do you have time to take a look? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything works as expected, the PR looks good to me, I just left a few remarks.
.breadcrumb { | ||
background: @component-background; | ||
border-bottom: 1px solid @border-color-split; | ||
margin-bottom: 16px; | ||
padding: 12px 24px; | ||
position: relative; | ||
display: block; | ||
} | ||
|
||
flink-refresh-download { | ||
position: absolute; | ||
right: 12px; | ||
top: 0; | ||
line-height: 47px; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We seem to have done some duplicate work with Task Managers
log list, can we make these codes reusable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
these two components look very similar, but the style is not the same(some border and full-screen style need to adjust according to different layout)
and they may have more different features in the future, like #10228, I think it would better not to create a share component between them
(reload)="reload()" | ||
(fullScreen)="toggleFullScreen($event)"> | ||
</flink-refresh-download> | ||
</div> | ||
<flink-monaco-editor [value]="logs"></flink-monaco-editor> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Feature works as expected but I have some remarks regarding the usability. If a user starts and stops the cluster multiple times locally, the log list gets confusing quickly, i.e., it is difficult to find the latest/active log file. See screenshot below: You can simulate this yourself by running:
For task manager logs it is similar but perhaps a bit better since there is a way to access the "main TM log" directly from the sub vertex page. Do you have any ideas how this can be improved? FLINK-16863 would not fully solve the above problem; if a user has many local TMs running, it could still be difficult to find the current/active JM log. cc: @jinglining |
Hi @GJL I have a discussion with @jinglining , what about the following solutions?
the we can get it from flink/flink-runtime/src/main/java/org/apache/flink/runtime/webmonitor/WebMonitorUtils.java Lines 71 to 75 in b41f09f
|
First of all, I am sorry that I did not see this problem earlier.
It would mitigate the issue. However, the user would still see additional log files belonging to other processes, e.g., when users are running multiple standalone TMs on the same host. Ideally, only files owned by the respective TM/JM process are listed. Therefore, an extension of your idea that @tillrohrmann had is to put all logs belonging to a single process into a separate directory. However, for a user who wants to configure custom log files, it could be difficult to predict the name of the log directory, which would render the whole feature useless. A (temporary) workaround could be to always show the main log and stdout file by default and make the log list a separate page. This would allow us to roll out the feature while not changing existing behavior. I think we should not make a decision on our own. Maybe it is acceptable to see other processes' log files. How about we bring this issue up on the dev mailing list and see what others are saying (especially the developers that voted on FLIP-103 in the first place)? |
I have bring up this issue in the mail list |
I have revert the deletion of the sdtout and logs page |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
Stdout
and Logs
work for me.
What is the purpose of the change
ref https://issues.apache.org/jira/browse/FLINK-17130
Brief change log
add JM log list
add JM log detail
Verifying this change
before:
after:
list:
log-detail from the list:
full screen:
Does this pull request potentially affect one of the following parts:
@Public(Evolving)
: (no)Documentation