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 9AAF518CC0 for ; Wed, 1 Jul 2015 21:17:05 +0000 (UTC) Received: (qmail 26773 invoked by uid 500); 1 Jul 2015 21:17:05 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 26735 invoked by uid 500); 1 Jul 2015 21:17:05 -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 26718 invoked by uid 99); 1 Jul 2015 21:17:05 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Jul 2015 21:17:05 +0000 Date: Wed, 1 Jul 2015 21:17:05 +0000 (UTC) From: "Dmytro Sen (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Resolved] (AMBARI-12063) Config groups can't be saved in some cases 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-12063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dmytro Sen resolved AMBARI-12063. --------------------------------- Resolution: Fixed {code} [INFO] Reactor Summary: [INFO] [INFO] Ambari Main ....................................... SUCCESS [1.218s] [INFO] Apache Ambari Project POM ......................... SUCCESS [0.005s] [INFO] Ambari Web ........................................ SUCCESS [30.363s] [INFO] Ambari Views ...................................... SUCCESS [1.855s] [INFO] Ambari Admin View ................................. SUCCESS [8.590s] [INFO] ambari-metrics .................................... SUCCESS [0.406s] [INFO] Ambari Metrics Common ............................. SUCCESS [1.097s] [INFO] Ambari Metrics Hadoop Sink ........................ SUCCESS [2.691s] [INFO] Ambari Metrics Flume Sink ......................... SUCCESS [1.439s] [INFO] Ambari Metrics Kafka Sink ......................... SUCCESS [7.451s] [INFO] Ambari Metrics Storm Sink ......................... SUCCESS [0.991s] [INFO] Ambari Metrics Collector .......................... SUCCESS [3:30.517s] [INFO] Ambari Metrics Monitor ............................ SUCCESS [1.311s] [INFO] Ambari Metrics Assembly ........................... SUCCESS [1:47.330s] [INFO] Ambari Server ..................................... SUCCESS [1:45:50.989s] [INFO] Ambari Agent ...................................... SUCCESS [18.725s] [INFO] Ambari Client ..................................... SUCCESS [0.028s] [INFO] Ambari Python Client .............................. SUCCESS [0.312s] [INFO] Ambari Groovy Client .............................. SUCCESS [8.571s] [INFO] Ambari Shell ...................................... SUCCESS [0.009s] [INFO] Ambari Python Shell ............................... SUCCESS [0.006s] [INFO] Ambari Groovy Shell ............................... SUCCESS [5.541s] [INFO] ------------------------------------------------------------------------ [INFO] BUILD SUCCESS {code} Committed to trunk and branch-2.1 > Config groups can't be saved in some cases > ------------------------------------------ > > Key: AMBARI-12063 > URL: https://issues.apache.org/jira/browse/AMBARI-12063 > Project: Ambari > Issue Type: Bug > Components: ambari-server > Affects Versions: 2.1.0 > Reporter: Dmytro Sen > Assignee: Dmytro Sen > Priority: Critical > Fix For: 2.1.0 > > Attachments: AMBARI-12063.patch > > > Go to HDFS config page on installed cluster. > Create config group (assigned hosts doesn't matter). > Change config dfs.namenode.handler.count and save. At this time it's ok. > Change dtnode_heapsize and click save. Server returns 500 error with no info about error. -- This message was sent by Atlassian JIRA (v6.3.4#6332)