ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vitaly Brodetskyi (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (AMBARI-3976) ambari-server setup -j option installs JDK to indicated location if it does not exist there
Date Wed, 15 Jan 2014 14:59:22 GMT

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

Vitaly Brodetskyi commented on AMBARI-3976:
-------------------------------------------

Review request: https://reviews.apache.org/r/16907/

> ambari-server setup -j option installs JDK to indicated location if it does not exist
there
> -------------------------------------------------------------------------------------------
>
>                 Key: AMBARI-3976
>                 URL: https://issues.apache.org/jira/browse/AMBARI-3976
>             Project: Ambari
>          Issue Type: Bug
>          Components: agent
>    Affects Versions: 1.5.0
>            Reporter: Jonathan Maron
>            Assignee: Vitaly Brodetskyi
>             Fix For: 1.5.0
>
>         Attachments: AMBARI-3976.patch
>
>
> As part of the savanna install of an ambari server I've added code to point to an already
installed JDK location:
> 2013-12-03 05:41:46.557 18771 DEBUG savanna.utils.remote [-] [dc1-master-001] Executing
"ambari-server setup -s -j /opt/jdk1.6.0_31 > /dev/null 2>&1" _log_command /root/dev/savanna/savanna/utils/remote.py:384
> The interesting thing I've discovered is that if the JDK does not exist in that location
the JDK is retrieved and installed in that location by ambari. I can't find any documentation
indicating that behavior. Is it valid for me to assume this is expected behavior that will
continue to be supported? It actually would simplify things for us (no need to check for the
existence of the JDK in expected location on a remote VM prior to installation), but in that
case I imagine this aspect of the feature should be documented and maintained going forward.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message