Mailing-List: contact issues-help@ambari.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ambari.apache.org
Date: Wed, 22 Jun 2016 21:07:16 +0000 (UTC)
From: "Zhe (Joe) Wang (JIRA)" <jira@apache.org>
To: issues@ambari.apache.org
Message-ID: <JIRA.12859410.1440617584000.1863.1466629636405@Atlassian.JIRA>
In-Reply-To: <JIRA.12859410.1440617584000@Atlassian.JIRA>
References: <JIRA.12859410.1440617584000@Atlassian.JIRA> <JIRA.12859410.1440617584734@arcas>
Subject: [jira] [Reopened] (AMBARI-12885) Dynamic stack extensions - install
 and upgrade support for custom services
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Wed, 22 Jun 2016 21:07:18 -0000


     [ https://issues.apache.org/jira/browse/AMBARI-12885?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhe (Joe) Wang reopened AMBARI-12885:
-------------------------------------

Brand new install ambari-server. Couldn't start ambari-server.
In /var/log/ambari-server/ambari-server-check-database.log, it says
{code}
2016-06-22 20:39:40,252 ERROR - Unexpected error, database check failed
com.google.inject.ProvisionException: Guice provision errors:

1) Error injecting method, javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: org.postgresql.util.PSQLException: ERROR: relation "extensionlink" does not exist
  Position: 64
Error Code: 0
Call: SELECT t1.link_id, t1.extension_id, t1.stack_id FROM stack t0, extensionlink t1 WHERE (((t0.stack_name = ?) AND (t0.stack_version = ?)) AND (t0.stack_id = t1.stack_id))
        bind => [2 parameters bound]
Query: ReadAllQuery(name="ExtensionLinkEntity.findByStack" referenceClass=ExtensionLinkEntity sql="SELECT t1.link_id, t1.extension_id, t1.stack_id FROM stack t0, extensionlink t1 WHERE (((t0.stack_name = ?) AND (t0.stack_version = ?)) AND (t0.stack_id = t1.stack_id))")
  at org.apache.ambari.server.api.services.AmbariMetaInfo.init(AmbariMetaInfo.java:261)
  at org.apache.ambari.server.api.services.AmbariMetaInfo.class(AmbariMetaInfo.java:135)
  while locating org.apache.ambari.server.api.services.AmbariMetaInfo

1 error
        at com.google.inject.internal.InjectorImpl$4.get(InjectorImpl.java:987)
        at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1013)
        at org.apache.ambari.server.checks.DatabaseConsistencyCheckHelper.checkServiceConfigs(DatabaseConsistencyCheckHelper.java:401)
        at org.apache.ambari.server.checks.DatabaseConsistencyChecker.main(DatabaseConsistencyChecker.java:115)
Caused by: javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
{code}

> Dynamic stack extensions - install and upgrade support for custom services
> --------------------------------------------------------------------------
>
>                 Key: AMBARI-12885
>                 URL: https://issues.apache.org/jira/browse/AMBARI-12885
>             Project: Ambari
>          Issue Type: New Feature
>          Components: ambari-agent, ambari-server, ambari-web
>            Reporter: Tim Thorpe
>            Assignee: Tim Thorpe
>         Attachments: AMBARI-12885 Example.pdf, AMBARI-12885.patch, Dynamic Stack Extensions - High Level Design v5.pdf
>
>
> The purpose of this proposal is to facilitate adding custom services to an existing stack.  Ideally this would support adding and upgrading custom services separately from the core services defined in the stack.  In particular we are looking at custom services that need to support several different stacks (different distributions of Ambari).  The release cycle of the custom services may be different from that of the core stack; that is, a custom service may be upgraded at a different rate than the core distribution itself and may be upgraded multiple times within the lifespan of a single release of the core distribution.    
> One possible approach to handling this would be dynamically extending a stack (after install time).  It would be best to extend the stack in packages where a stack extension package can have one or more custom services.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)