Mailing-List: contact issues-help@geode.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geode.apache.org
Date: Fri, 17 Nov 2017 21:30:00 +0000 (UTC)
From: "Jinmei Liao (JIRA)" <jira@apache.org>
To: issues@geode.apache.org
Message-ID: <JIRA.13119315.1510950725000.270376.1510954200347@Atlassian.JIRA>
In-Reply-To: <JIRA.13119315.1510950725000@Atlassian.JIRA>
References: <JIRA.13119315.1510950725000@Atlassian.JIRA> <JIRA.13119315.1510950725240@jira-lw-us.apache.org>
Subject: [jira] [Updated] (GEODE-3994) create async-event-queue command
 should fail if we are trying to create the queue with the same queueId but
 different attributes.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Fri, 17 Nov 2017 21:30:06 -0000


     [ https://issues.apache.org/jira/browse/GEODE-3994?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jinmei Liao updated GEODE-3994:
-------------------------------
    Description: 
create async-event-queue --id=queue --group=group1 --listener=xxx
create async-event-queue --id=queue --group=group2 --listener=yyy

Currently, if group1 and group2 have common members, the second command would fail partially, the queue is created on some member but not another, but the cluster configuration is updated already. Future server that might belong to both groups will have trouble creating the queue. It would be a good idea to check for unique queue name. Besides, they might give the same name with different listener, which will add to the confusion.

  was:
create async-event-queue --id=queue --group=group1 --listener=xxx
create async-event-queue --id=queue --group=group2 --listener=xxx

Currently, if group1 and group2 have common members, the second command would fail partially, the queue is created on some member but not another, but the cluster configuration is updated already. Future server that might belong to both groups will have trouble creating the queue. It would be a good idea to check for unique queue name. Besides, they might give the same name with different listener, which will add to the confusion.


> create async-event-queue command should fail if we are trying to create the queue with the same queueId but different attributes.
> ---------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: GEODE-3994
>                 URL: https://issues.apache.org/jira/browse/GEODE-3994
>             Project: Geode
>          Issue Type: Bug
>            Reporter: Jinmei Liao
>
> create async-event-queue --id=queue --group=group1 --listener=xxx
> create async-event-queue --id=queue --group=group2 --listener=yyy
> Currently, if group1 and group2 have common members, the second command would fail partially, the queue is created on some member but not another, but the cluster configuration is updated already. Future server that might belong to both groups will have trouble creating the queue. It would be a good idea to check for unique queue name. Besides, they might give the same name with different listener, which will add to the confusion.


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)