[
https://issues.apache.org/jira/browse/AMBARI-21942?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16170490#comment-16170490
]
Hudson commented on AMBARI-21942:
---------------------------------
SUCCESS: Integrated in Jenkins build Ambari-branch-2.6 #234 (See
[https://builds.apache.org/job/Ambari-branch-2.6/234/])
AMBARI-21942. Upgrade to IOP 4.2.5 from IOP 4.1 failed with combined (swagle:
[http://git-wip-us.apache.org/repos/asf?p=ambari.git&a=commit&h=6a6d29d58339c617e4a34907536b38e99732ee2c])
* (edit)
ambari-server/src/main/java/org/apache/ambari/server/upgrade/UpgradeCatalog260.java
> Upgrade to IOP 4.2.5 from IOP 4.1 failed with combined Solr host names longer
> than item_text column size in table upgrade_item
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: AMBARI-21942
> URL: https://issues.apache.org/jira/browse/AMBARI-21942
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.5.2
> Reporter: Siddharth Wagle
> Assignee: Siddharth Wagle
> Priority: Critical
> Fix For: 2.6.0
>
> Attachments: AMBARI-21942.patch
>
>
> Basically the problem here happens when Ambari is attempting to insert
> into the following upgrade_itme:item_text table:column,
> INSERT INTO upgrade_item (upgrade_item_id, hosts, item_text, stage_id,
> state, tasks, upgrade_group_id) VALUES (?, ?, ?, ?, ?, ?, ?)
> Using the message string for SOLR generated in the xml path below for
> 4.1->4.2.5 Upgrade.
> The file in question is:
> /var/lib/ambari-server/resources/stacks/BigInsights/4.1/upgrades/nonrolling-upgrade-4.2.5.xml
> The message string for SOLR includes all the SOLR node hostnames whose
> combined string length exceeds the column length defined for "item_text" of
> 1024 characters.
> {code}
> Error Code: 0
> Call: INSERT INTO upgrade_item (upgrade_item_id, hosts, item_text, stage_id,
> state, tasks, upgrade_group_id) VALUES (?, ?, ?, ?, ?, ?, ?)
> bind => [7 parameters bound]
> at
> org.eclipse.persistence.exceptions.DatabaseException.sqlException(DatabaseException.java:340)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.processExceptionForCommError(DatabaseAccessor.java:1620)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.executeJDK12BatchStatement(DatabaseAccessor.java:926)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatch(ParameterizedSQLBatchWritingMechanism.java:179)
> at
> org.eclipse.persistence.internal.databaseaccess.ParameterizedSQLBatchWritingMechanism.executeBatchedStatements(ParameterizedSQLBatchWritingMechanism.java:134)
> at
> org.eclipse.persistence.internal.databaseaccess.DatabaseAccessor.writesCompleted(DatabaseAccessor.java:1845)
> at
> org.eclipse.persistence.internal.sessions.AbstractSession.writesCompleted(AbstractSession.java:4300)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.writesCompleted(UnitOfWorkImpl.java:5592)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.acquireWriteLocks(UnitOfWorkImpl.java:1646)
> at
> org.eclipse.persistence.internal.sessions.UnitOfWorkImpl.commitTransactionAfterWriteChanges(UnitOfWorkImpl.java:1614)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
