[
https://issues.apache.org/jira/browse/AMBARI-19953?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15868462#comment-15868462
]
Hudson commented on AMBARI-19953:
---------------------------------
FAILURE: Integrated in Jenkins build Ambari-trunk-Commit #6752 (See
[https://builds.apache.org/job/Ambari-trunk-Commit/6752/])
AMBARI-19953: AMS HBase RegionServer process is still alive after (avijayan:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=2db72cdf667a174d43eb7fa3c45166b1734948ae])
* (edit)
ambari-server/src/main/resources/common-services/AMBARI_METRICS/0.1.0/package/scripts/ams_service.py
* (edit)
ambari-server/src/test/python/stacks/2.0.6/AMBARI_METRICS/test_metrics_collector.py
> AMS HBase RegionServer process is still alive after switching AMS to embedded
> mode
> ----------------------------------------------------------------------------------
>
> Key: AMBARI-19953
> URL: https://issues.apache.org/jira/browse/AMBARI-19953
> Project: Ambari
> Issue Type: Bug
> Components: ambari-metrics
> Affects Versions: 2.4.2
> Environment:
> Reporter: Qin Liu
> Assignee: Qin Liu
> Priority: Minor
> Fix For: trunk
>
> Attachments: AMBARI-19953.patch
>
>
> After switching AMS to embedded mode, AMS HBase region server process from
> previous AMS configs is still alive.
> Steps to reproduce:
> 1. install a cluster with AMS distributed mode
> 2. ps -elf | grep ams
> 3. switch AMS to embedded mode
> 4. restart AMS
> 5. ps -elf | grep ams and will see AMS HBase regionserver process from
> previous AMS distributed configs is still alive
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
