[rabbitmq-discuss] defining role type in a cluster

Alexandru Scvorţov alexandru at rabbitmq.com
Tue Sep 27 21:31:52 BST 2011


Hi Kyle,

> It does help, thanks.  It looks like each rabbit node 'remembers' whether it was set to be a disc or ram node.

They "remember" until they're reset.

> Leads to another question though...  Is it possible setup a primary and secondary disc node, where the secondary is a ram node unless the primary leaves the cluster?

There's no automatic way to do this in RabbitMQ.  Also, there's no way
to convert a standalone ram node into a disc node without losing the
information on it (because rabbit has to be stopped to do the
conversion, so the database contents will be lost).

Clustering in RabbitMQ is designed to improve scalability (more nodes =
higher capacity).  What you're looking for is High Availability.  There
are a few ways to achieve that with Rabbit; see our two guides (you sort
of described an active/passive scenario):
  Active/Passive HA: http://www.rabbitmq.com/pacemaker.html
  Active/Active HA: http://www.rabbitmq.com/ha.html

Cheers,
Alex

On Tue, Sep 27, 2011 at 04:17:01PM -0400, Kyle O'Donnell wrote:
> Hi Alex,
> 
> It does help, thanks.  It looks like each rabbit node 'remembers' whether it was set to be a disc or ram node.
> 
> Leads to another question though...  Is it possible setup a primary and secondary disc node, where the secondary is a ram node unless the primary leaves the cluster?
> 
> Thanks,
> Kyle
> 
> ----- Original Message -----
> From: "Alexandru Scvorţov" <alexandru at rabbitmq.com>
> To: "Kyle O'Donnell" <kyleo at 0b10.mx>
> Cc: rabbitmq-discuss at lists.rabbitmq.com
> Sent: Tuesday, September 27, 2011 8:07:43 AM
> Subject: Re: [rabbitmq-discuss] defining role type in a cluster
> 
> Hi Kyle,
> 
> > Does anyone know if it's possible to define whether a node in a cluster is a disc or ram node via the rabbitmq.config file?  I am trying to ensure that if a node leaves the cluster for some reason it comes back as the appropriate node type.
> 
> You can auto-configure the cluster by setting cluster_nodes in
> rabbitmq.config:
>   http://www.rabbitmq.com/clustering.html#auto-config
> 
> As with manual plugin configuration, the node type is implicit: if the
> current node is in the cluster node list, it will be disc; otherwise,
> it will be ram.
> 
> So, if the 'rabbit at rabbit1' clusters with ['rabbit at rabbit2',
> 'rabbit at rabbit3'], it will be a ram node.  If it clusters with
> ['rabbit at rabbit1', 'rabbit at rabbit2', 'rabbit at rabbit3'], it will be a
> disc node.  In other respects, both clusters are identical.
> 
> Note that any manual configuration (via "rabbitmqctl cluster ...") will
> take precedence over the config file.  You can remove the manual
> configuration by resetting the node (at which point, rabbit will use the
> settings in the config file).
> 
> Hope this helps.
> 
> Cheers,
> Alex
> 
> On Mon, Sep 26, 2011 at 09:28:58AM -0400, Kyle O'Donnell wrote:
> > Hi,
> >
> > Does anyone know if it's possible to define whether a node in a cluster is a disc or ram node via the rabbitmq.config file?  I am trying to ensure that if a node leaves the cluster for some reason it comes back as the appropriate node type.
> >
> > Thanks,
> > Kyle
> > _______________________________________________
> > rabbitmq-discuss mailing list
> > rabbitmq-discuss at lists.rabbitmq.com
> > https://lists.rabbitmq.com/cgi-bin/mailman/listinfo/rabbitmq-discuss


More information about the rabbitmq-discuss mailing list