[jira] Updated: (QPID-2029) Clustering and Management don't work well together

["john dunning (JIRA)" <qp...@incubator.apache.org>]

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

john dunning updated QPID-2029:
-------------------------------

    Attachment: object-names.diff

Attached is a patch with addresses part of this problem.

Essentially, the substance of this change is to stop depending on OIDs being sync'ed between members of a cluster.  That's extraordinarily difficult to get right, given the current structure of the code.

We allow for objects to have fairly free-form names, and rely on object hierarchy to provide unambiguous paths to objects.  We add a python script which relies on these ideas to validate that cluster members really do have "the same" state.


> Clustering and Management don't work well together
> --------------------------------------------------
>
>                 Key: QPID-2029
>                 URL: https://issues.apache.org/jira/browse/QPID-2029
>             Project: Qpid
>          Issue Type: Bug
>          Components: C++ Broker
>    Affects Versions: 0.5
>            Reporter: Ted Ross
>            Assignee: Ted Ross
>             Fix For: 0.7
>
>         Attachments: object-names.diff
>
>
> Several aspects of management of the C++ broker are not well integrated with clustering.
> 1)  object-ids assigned to management objects are not synchronized across nodes of a cluster.
> 2)  persistent object-ids are not synchronized across nodes of a cluster.
> 3)  cached data within the QMF broker are not synchronized.
> 4) next-object-id and reboot-sequence are not synchronized.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project:      http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org