• Glossary
  • Support
  • Downloads
  • DataStax Home
Get Live Help
Expand All
Collapse All

DataStax Streaming Home

Starlight For RabbitMQ Documentation

    • Frequently Asked Questions
    • Installation
    • Configuration
    • Operations
      • Pulsar protocol handler
      • Pulsar proxy extension
      • Security
      • Monitoring
      • Clustering
      • Metadata store
  • Starlight For RabbitMQ Documentation
  • Operations
  • Clustering
2.10.1.x 2.10.0.x
Edit this Page

Clustering

Multiple Starlight for RabbitMQ instances can be launched at the same time for scalability and high availability needs. The Starlight for RabbitMQ instances are stateless and can be started and stopped at will. They share their configuration in ZooKeeper so you can create, delete, bind, and unbind exchanges and queues on any Starlight for RabbitMQ instance. The configuration will be synchronized on the other Starlight for RabbitMQ instances.

Publishing messages can be done on any Starlight for RabbitMQ instance. On the receiving side, messages will be dispatched evenly to all connected AMQP consumers because the Pulsar subscriptions are shared.

Monitoring Metadata store

General Inquiries: +1 (650) 389-6000 info@datastax.com

© DataStax | Privacy policy | Terms of use

DataStax, Titan, and TitanDB are registered trademarks of DataStax, Inc. and its subsidiaries in the United States and/or other countries.

Apache, Apache Cassandra, Cassandra, Apache Tomcat, Tomcat, Apache Lucene, Apache Solr, Apache Hadoop, Hadoop, Apache Pulsar, Pulsar, Apache Spark, Spark, Apache TinkerPop, TinkerPop, Apache Kafka and Kafka are either registered trademarks or trademarks of the Apache Software Foundation or its subsidiaries in Canada, the United States and/or other countries.

Kubernetes is the registered trademark of the Linux Foundation.

landing_page landingpage