ambari-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jonathan Hurley (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (AMBARI-19194) Deployed Views Throw Exceptions On Ambari Server Startup
Date Thu, 15 Dec 2016 14:54:00 GMT

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

Jonathan Hurley updated AMBARI-19194:
-------------------------------------
    Attachment: AMBARI-19194.patch

> Deployed Views Throw Exceptions On Ambari Server Startup
> --------------------------------------------------------
>
>                 Key: AMBARI-19194
>                 URL: https://issues.apache.org/jira/browse/AMBARI-19194
>             Project: Ambari
>          Issue Type: Bug
>          Components: ambari-views
>    Affects Versions: 2.5.0
>            Reporter: Jonathan Hurley
>            Assignee: Jonathan Hurley
>            Priority: Critical
>             Fix For: 2.5.0
>
>         Attachments: AMBARI-19194.patch
>
>
> - Install an HDP 2.5 cluster with HDFS, YARN, MapR, and ZK
> -- Relevant views, like Capacity Scheduler, should be instantiated at this point
> - Restart Ambari Server
> {noformat}
> 12 Dec 2016 02:37:47,067  INFO [main] ViewRegistry:1796 - setting up logging for view
CAPACITY-SCHEDULER{1.0.0} as per property file view.log4j.properties
> 12 Dec 2016 02:37:47,112  INFO [main] ViewRegistry:1860 - Auto creating instance of view
CAPACITY-SCHEDULER for cluster cl1.
> 12 Dec 2016 02:37:47,165 ERROR [main] AmbariJpaLocalTxnInterceptor:180 - [DETAILED ERROR]
Rollback reason: 
> 12 Dec 2016 02:37:47,166 ERROR [main] AmbariJpaLocalTxnInterceptor:188 - [DETAILED ERROR]
Internal exception (1) : 
> 12 Dec 2016 02:37:47,167 ERROR [main] ViewRegistry:1867 - Can't auto create instance
of view CAPACITY-SCHEDULER for cluster cl1.  Caught exception :Exception [EclipseLink-4002]
(Eclipse Persistence Services - 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> 12 Dec 2016 02:37:47,168  INFO [main] ViewRegistry:1738 - View deployed: CAPACITY-SCHEDULER{1.0.0}.
> 12 Dec 2016 02:37:47,176  INFO [main] ViewRegistry:1705 - Reading view archive /var/lib/ambari-server/resources/views/files-2.5.0.0.453.jar.
> 12 Dec 2016 02:37:47,227  INFO [main] ViewRegistry:1796 - setting up logging for view
FILES{1.0.0} as per property file view.log4j.properties
> 12 Dec 2016 02:37:47,277  INFO [main] ViewRegistry:1860 - Auto creating instance of view
FILES for cluster cl1.
> 12 Dec 2016 02:37:47,285 ERROR [main] AmbariJpaLocalTxnInterceptor:180 - [DETAILED ERROR]
Rollback reason: 
> 12 Dec 2016 02:37:47,286 ERROR [main] AmbariJpaLocalTxnInterceptor:188 - [DETAILED ERROR]
Internal exception (1) : 
> 12 Dec 2016 02:37:47,287 ERROR [main] ViewRegistry:1867 - Can't auto create instance
of view FILES for cluster cl1.  Caught exception :Exception [EclipseLink-4002] (Eclipse Persistence
Services - 2.6.2.v20151217-774c696): org.eclipse.persistence.exceptions.DatabaseException
> {noformat}
> and 
> {noformat}
> 12 Dec 2016 17:49:57,423 ERROR [main] AmbariJpaLocalTxnInterceptor:180 - [DETAILED ERROR]
Rollback reason: 
> Local Exception Stack: 
> Exception [EclipseLink-4002] (Eclipse Persistence Services - 2.6.2.v20151217-774c696):
org.eclipse.persistence.exceptions.DatabaseException
> Internal Exception: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException:
Column 'resource_id' cannot be null
> Error Code: 1048
> {noformat}
> This seems to be due to how view syncing works with in-memory (not persisted) entities.
Because the {{ViewInstanceEntity}} is constructed in memory (and not retrieve from the DB),
it's incomplete and cannot be used for things like retrieving associated entities from.



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

Mime
View raw message