-
Notifications
You must be signed in to change notification settings - Fork 3.3k
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
HBASE-29028 Backport missing UI patches to branch-2.5 #6542
HBASE-29028 Backport missing UI patches to branch-2.5 #6542
Conversation
…e#4833) Signed-off-by: Andor Molnar <[email protected]> Signed-off-by: Balazs Meszaros <[email protected]> (cherry picked from commit dffc8e0)
…InfoServer (apache#5215) Other changes: - Ensure info server stops during stop() - Extract header and footer. This would fix the log level page layout for rest web UI (See HBASE-20693) - Add hostname in the landing page instead of just port similar to other web UIs Signed-off-by: Nick Dimiduk <[email protected]> (cherry picked from commit a683fcf)
Signed-off-by: Wellington Chevreuil <[email protected]> Signed-off-by: Bharath Vissapragada <[email protected]> Signed-off-by: Viraj Jasani <[email protected]> (cherry picked from commit 82e155e)
…he#5732) - Fixes the way logLevel page renders in UI Signed-off-by: Nick Dimiduk <[email protected]> (cherry picked from commit ede4ccd)
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Signed-off-by: Guangxu Cheng <[email protected]> (cherry picked from commit 9ad16aa)
…empty start key/end key (apache#2955) Signed-off-by: Duo Zhang <[email protected]> Signed-off-by: Pankaj Kumar<[email protected]> (cherry picked from commit 157200e)
… table page (apache#4793) Co-authored-by: zhengsicheng <[email protected]> Signed-off-by: Duo Zhang <[email protected]> (cherry picked from commit eb6b274)
…procedure.jsp while Master is initializing (apache#6152) Signed-off-by: Duo Zhang <[email protected]> (cherry picked from commit 3caaf2d)
…pache#5620) Co-authored-by: Haosen Chen <[email protected]> Signed-off-by: Duo Zhang <[email protected]> (cherry picked from commit e3a0174)
…elds before submit Signed-off-by: tedyu <[email protected]> (cherry picked from commit 6ce1136)
ed87ac8
to
a9d154d
Compare
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Hi @PDavid please let me know once this PR is ready for review |
Hi @NihalJain, |
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 may need to drop HBASE-27406 Make /prometheus endpoint accessible from HBase UI (#4833) as the feature is not even supported by backend.
Trying to open /prometheus give 404 with this change.
Hi @NihalJain, Many thanks for testing the changes. 👍
Very good catch, thanks. I was not aware and somehow did not found this. 🤦♂️ I'll have a look and fix this. Would it work if we keep the "Metrics" dropdown but remove the Prometheus links? So we would only have the "JMX" and "JMX with description" links there. What do you think? |
Sounds good to me! |
as the feature (HBASE-20904) is not even supported by backend.
Dropped a mail on dev thread to decide on whether we want to take this and other related changes in before the upcoming release. https://lists.apache.org/thread/86ds4dxprvyot243g3jg0ztxzjn5btrq FYI @PDavid CC: #6525 |
💔 -1 overall
This message was automatically generated. |
The spotless check itself was successful in the CI build but there was some other error:
Also run spotless check locally and was successful. |
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.
I see the branch-2 PR has been merged already, and that presumably the branch-2.6 (#6550) will be merged soon. This can go in to branch-2.5 after that. @NihalJain
Hi @NihalJain and @apurtell, Many thanks for the reviews. I think this is ready to be merged. |
Cherry-picked the following patches which were missing on branch-2.5 branch. Most of these applied as a clean cherry-pick (without conflicts). Unfortunately there were some which had conflicts and I manually resolved them.
Each commit message contains from which commit it was cherry-picked from.
Is it OK to have multiple patches in one PR like this or would you prefer having a separate PR for each commit?