Return-Path: 
 <dev-return-12722-apmail-brooklyn-dev-archive=brooklyn.apache.org@brooklyn.apache.org>
X-Original-To: apmail-brooklyn-dev-archive@minotaur.apache.org
Delivered-To: apmail-brooklyn-dev-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 7B7B718A26
	for <apmail-brooklyn-dev-archive@minotaur.apache.org>;
 Fri, 11 Dec 2015 10:24:11 +0000 (UTC)
Received: (qmail 48880 invoked by uid 500); 11 Dec 2015 10:24:11 -0000
Delivered-To: apmail-brooklyn-dev-archive@brooklyn.apache.org
Received: (qmail 48809 invoked by uid 500); 11 Dec 2015 10:24:11 -0000
Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@brooklyn.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@brooklyn.apache.org>
List-Post: <mailto:dev@brooklyn.apache.org>
List-Id: <dev.brooklyn.apache.org>
Reply-To: dev@brooklyn.apache.org
Delivered-To: mailing list dev@brooklyn.apache.org
Received: (qmail 48698 invoked by uid 99); 11 Dec 2015 10:24:11 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 11 Dec 2015 10:24:11 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id EF0E02C14F9
	for <dev@brooklyn.apache.org>; Fri, 11 Dec 2015 10:24:10 +0000 (UTC)
Date: Fri, 11 Dec 2015 10:24:10 +0000 (UTC)
From: "Aled Sage (JIRA)" <jira@apache.org>
To: dev@brooklyn.apache.org
Message-ID: <JIRA.12921026.1449829398000.334662.1449829450975@Atlassian.JIRA>
In-Reply-To: <JIRA.12921026.1449829398000@Atlassian.JIRA>
References: <JIRA.12921026.1449829398000@Atlassian.JIRA>
 <JIRA.12921026.1449829398467@arcas>
Subject: [jira] [Created] (BROOKLYN-202) managementPlaneId should not change
 on server restart
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394

Aled Sage created BROOKLYN-202:
----------------------------------

             Summary: managementPlaneId should not change on server restart
                 Key: BROOKLYN-202
                 URL: https://issues.apache.org/jira/browse/BROOKLYN-202
             Project: Brooklyn
          Issue Type: Bug
    Affects Versions: 0.8.0
            Reporter: Aled Sage


The {{managementContext.getManagementPlaneId()}} should stay the same when a Brooklyn server is restarted. If you have two brooklyn servers running in high-availability mode, then they should both return the same management plane id.

However, this is not currently true: the id changes on rebind; and in high-availability mode then each server has a different id.

Below is the javadoc from {{ManagementContext}} described the expected behaviour.

{noformat}
    /** 
     * UID for the Brooklyn management plane which this {@link ManagementContext} node is a part of.
     * <p>
     * Each Brooklyn entity is actively managed by a unique management plane 
     * whose ID which should not normally change for the duration of that entity, 
     * even though the nodes in that plane might, and the plane may go down and come back up. 
     * In other words the value of {@link Application#getManagementContext()#getManagementPlaneId()} 
     * will generally be constant (in contrast to {@link #getManagementNodeId()}).
     * <p>
     * This value should not be null unless the management context is a non-functional
     * (non-deployment) instance. */
    String getManagementPlaneId();
    
    /** 
     * UID for this {@link ManagementContext} node (as part of a single management plane).
     * <p>
     * No two instances of {@link ManagementContext} should ever have the same node UID. 
     * The value of {@link Application#getManagementContext()#getManagementNodeId()} may
     * change many times (in contrast to {@link #getManagementPlaneId()}). 
     * <p>
     * This value should not be null unless the management context is a non-functional
     * (non-deployment) instance. */
    String getManagementNodeId();
{noformat}

I encountered this with 0.9.0-SNAPSHOT. I ran {{brooklyn launch --persist auto --persistenceDir /Users/aled/temp/empty}}, then restarted. I also then ran a second instance (thus in "HA STANDBY" mode), and got that management plane id via the groovy console.




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)