[ 
https://issues.apache.org/jira/browse/TRAFODION-1989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15968308#comment-15968308
 ] 

ASF GitHub Bot commented on TRAFODION-1989:
-------------------------------------------

GitHub user svarnau opened a pull request:

    https://github.com/apache/incubator-trafodion/pull/1064

    [TRAFODION-1989] Add earlier fix to ambari installer

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/svarnau/incubator-trafodion master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-trafodion/pull/1064.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1064
    
----
commit 4ce851bceeb0906f34b17edcb245f7234a25fb19
Author: Steve Varnau <svar...@apache.org>
Date:   2017-04-13T22:06:25Z

    [TRAFODION-1989] Add earlier fix to ambari installer

----


> after uninstall, and reinstall again, dcscheck report dcs master not up
> -----------------------------------------------------------------------
>
>                 Key: TRAFODION-1989
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-1989
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: installer
>            Reporter: liu ming
>            Assignee: Steve Varnau
>
> in the same cluster, one install a trafodion version.
> then use trafodion_uninstaller to remove the installation.
> later at same cluster, install again via trafodion_install
> after the new installation, dcscheck fail.
> jps cannot show related DCS java processes, but those processes are up and 
> running.
> It is due to a legacy /tmp/hsperfdata_trafodion direcotry belong to the 
> previous trafodion user. The new user cannot write into this folder, but jps 
> rely on it to work correct. And dcscheck rely on jps to work correctly.
> Either installer remove that legacy directory, or uninstaller remove it. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to