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 1D011102EE for ; Sat, 15 Mar 2014 16:56:47 +0000 (UTC) Received: (qmail 56894 invoked by uid 500); 15 Mar 2014 16:56:46 -0000 Delivered-To: apmail-ambari-dev-archive@ambari.apache.org Received: (qmail 56758 invoked by uid 500); 15 Mar 2014 16:56:44 -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 56429 invoked by uid 99); 15 Mar 2014 16:56:43 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 15 Mar 2014 16:56:43 +0000 Date: Sat, 15 Mar 2014 16:56:43 +0000 (UTC) From: "Andrew Onischuk (JIRA)" To: dev@ambari.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (AMBARI-5098) HBaseRegionServer requires multiple retries to be stopped during reassigning NameNode after EnablingHA MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Andrew Onischuk created AMBARI-5098: --------------------------------------- Summary: HBaseRegionServer requires multiple retries to be stopped during reassigning NameNode after EnablingHA Key: AMBARI-5098 URL: https://issues.apache.org/jira/browse/AMBARI-5098 Project: Ambari Issue Type: Bug Reporter: Andrew Onischuk Assignee: Andrew Onischuk

STR:
1. Install hadoop.
2. Enable HA.
3. Stop StandByNameNode on host-2.
4. Start ReassignNameNode wizard for the stopped StandByNameNode from host2 -> host3.
5. On the ConfigureComponents page StopAllServices fails for HBaseRegionServer Stop on host2. It required 3 retries, which were hanging for a while, to stop the component.
6. After that the wizard was proceeded successfully till the end without other issues.

It looks like a duplicate of BUG-9743.

-- This message was sent by Atlassian JIRA (v6.2#6252)