[ 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-subscr...@qpid.apache.org