Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 8D93C200D08 for ; Thu, 7 Sep 2017 01:38:05 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 8BDCD1609E2; Wed, 6 Sep 2017 23:38:05 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id AB6001609DB for ; Thu, 7 Sep 2017 01:38:04 +0200 (CEST) Received: (qmail 55706 invoked by uid 500); 6 Sep 2017 23:38:02 -0000 Mailing-List: contact issues-help@geode.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@geode.apache.org Delivered-To: mailing list issues@geode.apache.org Received: (qmail 55697 invoked by uid 99); 6 Sep 2017 23:38:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 06 Sep 2017 23:38:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 76868C5AB5 for ; Wed, 6 Sep 2017 23:38:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -99.202 X-Spam-Level: X-Spam-Status: No, score=-99.202 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id N80NiTNM8SJ5 for ; Wed, 6 Sep 2017 23:38:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 3E6A25FD48 for ; Wed, 6 Sep 2017 23:38:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id AF3A5E00C9 for ; Wed, 6 Sep 2017 23:38:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 591CB23F0D for ; Wed, 6 Sep 2017 23:38:00 +0000 (UTC) Date: Wed, 6 Sep 2017 23:38:00 +0000 (UTC) From: "Udo Kohlmeyer (JIRA)" To: issues@geode.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (GEODE-3567) Exporting configuration from GFSH causes multiple cacheservers to be listed MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 06 Sep 2017 23:38:05 -0000 [ https://issues.apache.org/jira/browse/GEODE-3567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Udo Kohlmeyer updated GEODE-3567: --------------------------------- Description: When running the following steps, ends up causing the `export config` command to list multiple `` entries to be created in the exported `cache.xml` {code} start locator --name=locator --enable-cluster-configuration=true --J=-Dgemfire.hostname-for-clients=bob start server --name=server --use-cluster-configuration=true --server-port=0 --hostname-for-clients=bob3 start server --name=server2 --use-cluster-configuration=true --server-port=0 --group=serverGROUP2 --hostname-for-clients=bob2 export cluster-configuration --zip-file-name=./backup1.zip export config --dir=./serversBack1 stop server --name=server2 start server --name=server2 --use-cluster-configuration=true --server-port=0 --group=serverGROUP2 --hostname-for-clients=bob2 export config --dir=./serversBack2 create disk-store --name=diskstore1 --dir=./ds1 create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW --disk-store=diskstore1 create region --name=TestRegion --type=REPLICATE_PERSISTENT_OVERFLOW --disk-store=diskstore1 create region --name=TestRegion10 --type=REPLICATE --group=serverGROUP2 export cluster-configuration --zip-file-name=./backup2.zip export config --dir=./serversBack3 stop server --name=server2 start server --name=server2 --use-cluster-configuration=true --server-port=0 --group=serverGROUP2 --hostname-for-clients=bob2 export config --dir=./serversBack4 {code} {code} {code} was: When running the following steps, ends up causing the `export config` command to list multiple `` entries to be created in the exported `cache.xml` {code} start locator --name=locator --enable-cluster-configuration=true --J=-Dgemfire.hostname-for-clients=bob start server --name=server --use-cluster-configuration=true --server-port=0 --hostname-for-clients=bob3 start server --name=server2 --use-cluster-configuration=true --server-port=0 --group=serverGROUP2 --hostname-for-clients=bob2 export cluster-configuration --zip-file-name=./backup1.zip export config --dir=./serversBack1 stop server --name=server2 start server --name=server2 --use-cluster-configuration=true --server-port=0 --group=serverGROUP2 --hostname-for-clients=bob2 export config --dir=./serversBack2 create disk-store --name=diskstore1 --dir=./ds1 create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW --disk-store=diskstore1 create region --name=TestRegion --type=REPLICATE_PERSISTENT_OVERFLOW --disk-store=diskstore1 create region --name=TestRegion10 --type=REPLICATE --group=serverGROUP2 export cluster-configuration --zip-file-name=./backup2.zip export config --dir=./serversBack3 stop server --name=server2 start server --name=server2 --use-cluster-configuration=true --server-port=0 --group=serverGROUP2 --hostname-for-clients=bob2 export config --dir=./serversBack4 {code} > Exporting configuration from GFSH causes multiple cacheservers to be listed > --------------------------------------------------------------------------- > > Key: GEODE-3567 > URL: https://issues.apache.org/jira/browse/GEODE-3567 > Project: Geode > Issue Type: Bug > Components: configuration, gfsh > Affects Versions: 1.0.0-incubating, 1.1.0, 1.2.0 > Reporter: Udo Kohlmeyer > > When running the following steps, ends up causing the `export config` command to list multiple `` entries to be created in the exported `cache.xml` > {code} > start locator --name=locator --enable-cluster-configuration=true --J=-Dgemfire.hostname-for-clients=bob > start server --name=server --use-cluster-configuration=true --server-port=0 --hostname-for-clients=bob3 > start server --name=server2 --use-cluster-configuration=true --server-port=0 --group=serverGROUP2 --hostname-for-clients=bob2 > export cluster-configuration --zip-file-name=./backup1.zip > export config --dir=./serversBack1 > stop server --name=server2 > start server --name=server2 --use-cluster-configuration=true --server-port=0 --group=serverGROUP2 --hostname-for-clients=bob2 > export config --dir=./serversBack2 > create disk-store --name=diskstore1 --dir=./ds1 > create region --name=TestRegion2 --type=REPLICATE_PERSISTENT_OVERFLOW --disk-store=diskstore1 > create region --name=TestRegion --type=REPLICATE_PERSISTENT_OVERFLOW --disk-store=diskstore1 > create region --name=TestRegion10 --type=REPLICATE --group=serverGROUP2 > export cluster-configuration --zip-file-name=./backup2.zip > export config --dir=./serversBack3 > stop server --name=server2 > start server --name=server2 --use-cluster-configuration=true --server-port=0 --group=serverGROUP2 --hostname-for-clients=bob2 > export config --dir=./serversBack4 > {code} > {code} > > > > {code} -- This message was sent by Atlassian JIRA (v6.4.14#64029)