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

HDDS-11120. Rich rebalancing status info #6911

Merged
merged 27 commits into from
Jul 22, 2024

Conversation

juncevich
Copy link
Contributor

@juncevich juncevich commented Jul 8, 2024

What changes were proposed in this pull request?

Problem: rebalancing status show information only about running rebalancing.

Need to add additional information in rebalancing status cli command.

  1. Rebalancing start time
  2. Rebalancing parameters
  3. How many containers need to be balanced and how many containers from then still unbalanced
  4. How many data in Gb need to transfered in general and how many untransfered yet
  5. Which datanodes took a part in rebalancing

As idea to use flags for command to get more information about rebalancing status. For example use v or -verbose.

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-11120

How was this patch tested?

Patch tested by unit tests.

@juncevich juncevich marked this pull request as draft July 8, 2024 16:20
@kerneltime
Copy link
Contributor

@juncevich thank you for taking the time to post a PR, can you please follow the contributing process and create a Jira describing your change and then update the description of the PR to reflect the PR specific details?

@juncevich juncevich changed the title Rich balancing status info HDDS-11120. Rich rebalancing status info Jul 8, 2024
@juncevich
Copy link
Contributor Author

@juncevich thank you for taking the time to post a PR, can you please follow the contributing process and create a Jira describing your change and then update the description of the PR to reflect the PR specific details?

@kerneltime thank you for notice about PR. I tried to change PR describe information. But i have a question. Is it critical, that branch doesn't contain task number? Do i have reopen PR with properly named branch?

@adoroszlai
Copy link
Contributor

Is it critical, that branch doesn't contain task number? Do i have reopen PR with properly named branch?

No need to reopen, you are free to use any branch name. Including Jira issue ID in the branch name helps folks with multiple tasks organize their own branches.

@juncevich juncevich marked this pull request as ready for review July 12, 2024 10:00
Copy link
Contributor

@adoroszlai adoroszlai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @juncevich for the patch, and for iterating on it as draft.

I haven't checked the balancer-specific part, am only commenting on some general items.

@juncevich
Copy link
Contributor Author

Thanks @juncevich for the patch, and for iterating on it as draft.

I haven't checked the balancer-specific part, am only commenting on some general items.

Hi, @adoroszlai! Cool!. Thank you for your review. Will fix notices.

@juncevich juncevich requested a review from adoroszlai July 15, 2024 06:26
Copy link
Contributor

@adoroszlai adoroszlai left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @juncevich for updating the patch.

Most of the changes in response to previous review comments are fine.

@juncevich juncevich requested a review from adoroszlai July 17, 2024 09:55
@adoroszlai
Copy link
Contributor

@juncevich GitHub allows restricting re-run to failed checks, which saves time and resources compared to full run. It also avoids the situation where each new full run may have different intermittent failures. So please don't push empty commit to restart checks.

@juncevich
Copy link
Contributor Author

juncevich commented Jul 19, 2024

@juncevich GitHub allows restricting re-run to failed checks, which saves time and resources compared to full run. It also avoids the situation where each new full run may have different intermittent failures. So please don't push empty commit to restart checks.

Sorry, bit i didn't found that buttons in build.
изображение

@adoroszlai
Copy link
Contributor

Sorry, bit i didn't foind that buttons in build

It requires write access to the repository, so committers can re-run failed tests for you.

@juncevich
Copy link
Contributor Author

Sorry, bit i didn't foind that buttons in build

It requires write access to the repository, so committers can re-run failed tests for you.

Have I ask any comitter to rerun task ?

@adoroszlai
Copy link
Contributor

adoroszlai commented Jul 19, 2024

Have I ask any comitter to rerun task ?

In this case it's not needed, because the new commit requires a new full run anyway, which I have already triggered.

Copy link
Contributor

@ivandika3 ivandika3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@juncevich Thanks for the improvement. Overall LGTM. Only a few nitpicks.

Copy link
Contributor

@ivandika3 ivandika3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the update, LGTM +1.

@ivandika3 ivandika3 merged commit a5e420c into apache:master Jul 22, 2024
39 checks passed
@ivandika3
Copy link
Contributor

Thanks @juncevich for the patch, @adoroszlai for the review.

@juncevich juncevich deleted the rich-status-info branch July 22, 2024 13:48
errose28 added a commit to errose28/ozone that referenced this pull request Jul 30, 2024
…-delete

* HDDS-10239-container-reconciliation: (184 commits)
  HDDS-10373. Implement framework for capturing Merkle Tree Metrics. (apache#6864)
  HDDS-11188. Initial setup for new UI layout and enable users to switch to new UI (apache#6953)
  HDDS-11120. Rich rebalancing status info (apache#6911)
  HDDS-11187. Fix Event Handling in Recon OMDBUpdatesHandler to Prevent ClassCastException. (apache#6950)
  HDDS-11213. Bump commons-daemon to 1.4.0 (apache#6971)
  HDDS-11212. Bump commons-net to 3.11.1 (apache#6973)
  HDDS-11211. Bump assertj-core to 3.26.3 (apache#6972)
  HDDS-11210. Bump log4j2 to 2.23.1 (apache#6970)
  HDDS-11150. Recon Overview page crashes due to failed API Calls (apache#6944)
  HDDS-11183. Keys from DeletedTable and DeletedDirTable of AOS should be deleted on batch operation while creating a snapshot (apache#6946)
  HDDS-11198. Fix Typescript configs for Recon (apache#6961)
  HDDS-11180. Simplify HttpServer2#inferMimeType return statement (apache#6963)
  HDDS-11194. OM missing audit log for upgrade (apache#6958)
  HDDS-10389. Implement a search feature for users to locate open keys within the Open Keys Insights section. (apache#6231)
  HDDS-10561. Dashboard for delete key metrics (apache#6948)
  HDDS-11192. Increase SPNEGO URL test coverage (apache#6956)
  HDDS-11179. DBConfigFromFile#readFromFile result of toIOException not thrown (apache#6957)
  HDDS-11186. First container log missing from bundle (apache#6952)
  HDDS-10844. Clarify snapshot create error message. (apache#6955)
  HDDS-11166. Switch to Rocky Linux-based ozone-runner (apache#6942)
  ...
@siddhantsangwan
Copy link
Contributor

@juncevich thanks for contributing this, it's a very useful feature. I opened https://issues.apache.org/jira/browse/HDDS-11385 to fix bugs and make improvements in this area. Please see if you're interested in working on any of the open tasks!

@juncevich
Copy link
Contributor Author

@siddhantsangwan, thanks. I can take this task. Can you describe problems in Jira task?

@siddhantsangwan
Copy link
Contributor

@siddhantsangwan, thanks. I can take this task. Can you describe problems in Jira task?

I've already described problems in sub-tasks. Let me know if you have any questions. Also opened a PR - #7134.

@juncevich
Copy link
Contributor Author

https://issues.apache.org/jira/browse/HDDS-11385

Thanks. Didn't see subtask list.

xichen01 pushed a commit to xichen01/ozone that referenced this pull request Sep 16, 2024
xichen01 pushed a commit to xichen01/ozone that referenced this pull request Sep 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants