[
https://issues.apache.org/jira/browse/AMBARI-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13563107#comment-13563107
]
Hitesh Shah commented on AMBARI-1256:
-------------------------------------
Should a version be stored in the DB for handling future upgrades where 1.2.0
could be upgraded to 1.2.5 or 1.3.0 - allowing relevant upgrade scripts to be
applied as needed via detection of the version info in the DB?
> 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-II.patch, 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
