You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Ted Ross (JIRA)" <qp...@incubator.apache.org> on 2009/08/05 15:53:14 UTC
[jira] Created: (QPID-2029) Clustering and Management don't work
well together
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.6
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.
--
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
[jira] Commented: (QPID-2029) Clustering and Management don't work
well together
Posted by "Alan Conway (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12830256#action_12830256 ]
Alan Conway commented on QPID-2029:
-----------------------------------
The python test needs to throw an exception if it fails, so e.g. you could do
assert os.system("verify_cluster_objects") == 0
I would delete the obsolete stuff rather than #if 0, it just leads to clutter. SVN has the old code if we ever need it.
Why does verify_cluster_objects create bindings and exchanges? I thought the idea was just to verify consistency, we can do arbitrary stuff to the cluster and the run the verifier.
It would be nice to have this loadable as a python module so we can use it directly rather than os.system but that can be done later.
The verify_cluster_objects script will be great to have!
> 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
[jira] Updated: (QPID-2029) Clustering and Management don't work
well together
Posted by "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
[jira] Updated: (QPID-2029) Clustering and Management don't work
well together
Posted by "Ted Ross (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Ted Ross updated QPID-2029:
---------------------------
Description:
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.
was:
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.
> 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.6
>
>
> 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
[jira] Updated: (QPID-2029) Clustering and Management don't work
well together
Posted by "Andrew Stitcher (JIRA)" <qp...@incubator.apache.org>.
[ https://issues.apache.org/jira/browse/QPID-2029?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andrew Stitcher updated QPID-2029:
----------------------------------
Fix Version/s: (was: 0.6)
0.7
> 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
>
>
> 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
[jira] Updated: (QPID-2029) Clustering and Management don't work
well together
Posted by "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-2.diff
Thanks Alan for the feedback!
Here's a revised patch. I finished the cleanup, got rid of the obsolete stuff; thought I got it all before, mea typo
I took the extra debug code out of verify. That was leftover from a previous debugging attempt, and you're right, it doesn't belong there.
I tried a couple things to make verify be loadable, but I couldn't work out how to do that in python, my simple attempts failed. Hints?
> 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-2.diff, 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