-
Notifications
You must be signed in to change notification settings - Fork 686
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
GEODE-9478: Fix status --dir to use file controller #6737
base: develop
Are you sure you want to change the base?
Conversation
9eeb75c
to
0371b8f
Compare
0371b8f
to
c6e316d
Compare
Thanks for working on this change! Please give me a day or so to finish reviewing. |
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 would remove the @throws IllegalArgumentException
javadoc clause on the new constructors of FileProcessController
and then go ahead and merge.
* | ||
* @throws IllegalArgumentException if pid is not a positive integer |
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.
Delete throws since pid is not a parameter on this constructor.
* | ||
* @throws IllegalArgumentException if pid is not a positive integer |
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.
Delete throws since pid is not a parameter on this constructor.
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.
Thanks for pointing this out. Change done!
cb6b1a4
to
7ceda07
Compare
Consider adding the |
Thanks for mentioning that. I tend to forget about Windows :) |
this PR appears to be abandoned (although I'm not sure why), should it be merged or closed? |
I haven't look into this for a long time. I'd like to get this merged if possible, so I'll work on the merge conflicts and try to get the missing reviews, if any others are needed |
59b1701
to
f7182fe
Compare
f7182fe
to
53338bc
Compare
- Previously when you only specified --dir option the PID was read from the member workDir and the status request was attempted to solved by using the attachment API, and after that JMX interface. But given only --dir was specified the controller resolving the request should be FileProcessController instead. - Logic has been changed for both servers and locators to always use FileProcessConroller whenever only --dir flag is specified. - Added an UT to verify new code. - Modified several ITs to verify the new behaviour. - Deleted the following ITs which no longer apply with the new logic: * statusWithEmptyPidFileThrowsIllegalArgumentException * statusWithEmptyWorkingDirectoryReturnsNotRespondingWithDetails * statusWithStalePidFileReturnsNotResponding
- Removed throws in javadoc given new constructors doesn't have any PID
53338bc
to
1ae64a5
Compare
the member workDir and the status request was attempted to solved by
using the attachment API, and after that JMX interface.
But given only --dir was specified the controller resolving the
request should be FileProcessController instead.
FileProcessConroller whenever only --dir flag is specified.
Thank you for submitting a contribution to Apache Geode.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced in the commit message?
Has your PR been rebased against the latest commit within the target branch (typically
develop
)?Is your initial contribution a single, squashed commit?
Does
gradlew build
run cleanly?Have you written or updated unit tests to verify your changes?
[N/A] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
Note:
Please ensure that once the PR is submitted, check Concourse for build issues and
submit an update to your PR as soon as possible. If you need help, please send an
email to [email protected].