[AMBARI-23415] Remove unwanted trailing slash at the end of hbase_pid… - #845
Merged
Conversation
…_dir path in ams-hbase-env
|
Refer to this link for build results (access rights to CI server needed): |
Contributor
Author
|
@avijayanhwx |
rlevas
approved these changes
Apr 5, 2018
Contributor
|
retest this please |
|
Refer to this link for build results (access rights to CI server needed): |
avijayanhwx
approved these changes
Apr 16, 2018
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
…_dir path in ams-hbase-env
What changes were proposed in this pull request?
While starting the AMS collector we can see that it has two slash in the PID file path
/var/run/ambari-metrics-collector//hbase-ams-regionserver.pid/var/run/ambari-metrics-collector//hbase-ams-master.pidIt does not look good and seems error prone. It should be removed.
How was this patch tested?
Tested the fix manually.
Build was successful.