[
https://issues.apache.org/jira/browse/AMBARI-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sumit Mohanty updated AMBARI-1256:
----------------------------------
Attachment: Ambari-upgrade-1256.patch
The SQL file for upgrade includes the version number assuming all upgrade files
for multiple versions are at the same location
/var/lib/ambari-server/resources. Other option is to create version specific
directories and drop the similarly named files (this could be confusing as file
names will not capture version info).
Are their any more sanity checks necessary during upgrade (in ambari-server.py
file)?
> Host registration can fail due to mount point info not fitting
> ambari.hosts::disks_info column
> ----------------------------------------------------------------------------------------------
>
> Key: AMBARI-1256
> URL: https://issues.apache.org/jira/browse/AMBARI-1256
> Project: Ambari
> Issue Type: Bug
> Affects Versions: 1.2.0
> Reporter: Sumit Mohanty
> Assignee: Sumit Mohanty
> Priority: Critical
> Fix For: 1.2.1
>
> Attachments: Ambari-upgrade-1256.patch
>
>
> Currently disks_info column is 2000 characters long.
> For one of the users, this was not big enough to fit all the mount points
> detected (they had 40+ mount points on their hosts).
> We made this disks_info column size to be 10000 to workaround this issue.
> Ensure that upgrade supports performing schema alteration on an existing
> installation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
