You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by "Alejandro Fernandez (JIRA)" <ji...@apache.org> on 2015/03/17 02:29:39 UTC
[jira] [Commented] (AMBARI-10098)
https://hortonworks.jira.com/browse/BUG-33244
[ https://issues.apache.org/jira/browse/AMBARI-10098?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14364380#comment-14364380 ]
Alejandro Fernandez commented on AMBARI-10098:
----------------------------------------------
Fix is in Ambari-DDL-MySQL-CREATE.sql
{code}
INSERT INTO ambari_sequences(sequence_name, sequence_value) values ('upgrade_group_id_seq', 0);
{code}
> https://hortonworks.jira.com/browse/BUG-33244
> ---------------------------------------------
>
> Key: AMBARI-10098
> URL: https://issues.apache.org/jira/browse/AMBARI-10098
> Project: Ambari
> Issue Type: Bug
> Components: ambari-server
> Affects Versions: 2.0.0
> Reporter: Alejandro Fernandez
> Assignee: Alejandro Fernandez
> Fix For: 2.0.0
>
>
> Tried to make an RU,
> * Deployed clustered, enabled Namenode HA, distributed bits
> * Attempt to begin an RU (through both UI and curl call)
> {code}
> curl -X POST -u admin:admin -H 'X-Requested-By:1' http://server:8080/api/v1/clusters/cl1/upgrades -d '{"Upgrade": {"repository_version": "2.2.3.0-2610"}}'
> {
> "status": 500,
> "message": "\nException Description: Error preallocating sequence numbers. The sequence table information is not complete."
> }
> {code}
> {code}
> Exception Description: Error preallocating sequence numbers. The sequence table information is not complete.
> {code}
> Saw this on two clusters (Ubuntu and SP3) with MySQL Ambari DB that I deployed to EC2.
> Ambari version, 2.0.0-137
> Database: MySQL
> {code}
> mysql> select * from ambari_sequences;
> +--------------------------+----------------+
> | sequence_name | sequence_value |
> +--------------------------+----------------+
> | alert_current_id_seq | 132 |
> | alert_definition_id_seq | 64 |
> | alert_group_id_seq | 20 |
> | alert_history_id_seq | 456 |
> | alert_notice_id_seq | 0 |
> | alert_target_id_seq | 0 |
> | cluster_id_seq | 2 |
> | cluster_version_id_seq | 2 |
> | configgroup_id_seq | 1 |
> | config_id_seq | 95 |
> | group_id_seq | 1 |
> | host_role_command_id_seq | 1001 |
> | host_version_id_seq | 12 |
> | member_id_seq | 1 |
> | operation_level_id_seq | 5 |
> | permission_id_seq | 5 |
> | principal_id_seq | 2 |
> | principal_type_id_seq | 3 |
> | privilege_id_seq | 1 |
> | repo_version_id_seq | 2 |
> | requestschedule_id_seq | 1 |
> | resourcefilter_id_seq | 20 |
> | resource_id_seq | 4 |
> | resource_type_id_seq | 8 |
> | service_config_id_seq | 31 |
> | upgrade_id_seq | 2 |
> | upgrade_item_id_seq | 0 |
> | user_id_seq | 2 |
> | viewentity_id_seq | 0 |
> | view_instance_id_seq | 2 |
> +--------------------------+----------------+
> 30 rows in set (0.00 sec)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)