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-12011. Show PID of running service #7648

Merged
merged 1 commit into from
Jan 6, 2025

Conversation

sarvekshayr
Copy link
Contributor

What changes were proposed in this pull request?

The check added in HDDS-11727 only shows if the service is running. Show the PID of the process found to be running as well.

What is the link to the Apache JIRA

HDDS-12011

How was this patch tested?

Tested the patch on a docker cluster.

bash-5.1$ ozone repair om fso-tree --db /data/metadata/om.db
ATTENTION: Running as user hadoop. Make sure this is the same user used to run the Ozone process. Are you sure you want to continue (y/N)? y
Run as user: hadoop
Error: OM is currently running on this host with PID 7. Stop the service before running the repair tool.
bash-5.1$ ozone repair om fso-tree --db /data/metadata/om.db --force
ATTENTION: Running as user hadoop. Make sure this is the same user used to run the Ozone process. Are you sure you want to continue (y/N)? y
Run as user: hadoop
Warning: --force flag used. Proceeding despite OM being detected as running with PID 7.
FSO Repair Tool is running in debug mode

Copy link
Contributor

@Tejaskriya Tejaskriya 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 patch @sarvekshayr, LGTM

@nandakumar131 nandakumar131 merged commit 3d35b01 into apache:master Jan 6, 2025
42 checks passed
@nandakumar131
Copy link
Contributor

Thanks @sarvekshayr for the contribution and @Tejaskriya for the review!

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.

3 participants