geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jinmei Liao (JIRA)" <j...@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.
Date Fri, 17 Nov 2017 21:29:01 GMT

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

Jinmei Liao updated GEODE-3994:
-------------------------------
    Summary: create async-event-queue command should fail if we are trying to create the queue
with the same queueId but different attributes.  (was: create async-event-queue command should
fail if we are trying to create the queue with the same queueId on different groups)

> 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=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.



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

Mime
View raw message