Return-Path: X-Original-To: apmail-ambari-dev-archive@www.apache.org Delivered-To: apmail-ambari-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id BF83D1762A for ; Tue, 17 Mar 2015 01:31:38 +0000 (UTC) Received: (qmail 52334 invoked by uid 500); 17 Mar 2015 01:31:38 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 52306 invoked by uid 500); 17 Mar 2015 01:31:38 -0000 Mailing-List: contact dev-help@ambari.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ambari.apache.org Delivered-To: mailing list dev@ambari.apache.org Received: (qmail 52040 invoked by uid 99); 17 Mar 2015 01:31:38 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 17 Mar 2015 01:31:38 +0000 Date: Tue, 17 Mar 2015 01:31:38 +0000 (UTC) From: "Alejandro Fernandez (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (AMBARI-10098) RU - Unable to begin RU due to MySQL "Error preallocating sequence numbers" MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/AMBARI-10098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alejandro Fernandez updated AMBARI-10098: ----------------------------------------- Attachment: AMBARI-10098.patch > RU - Unable to begin RU due to MySQL "Error preallocating sequence numbers" > --------------------------------------------------------------------------- > > 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 > Labels: rolling_upgrade > Fix For: 2.0.0 > > Attachments: AMBARI-10098.patch > > > 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)