feature: Allow ram clusters, by exposing cluster_node_type

Bug #1448251 reported by Jorge Niedbalski
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack RabbitMQ Server Charm
Triaged
Wishlist
Jorge Niedbalski
rabbitmq-server (Juju Charms Collection)
Invalid
Wishlist
Jorge Niedbalski

Bug Description

There are some scenarios on which by performance issues is required to have in memory metadata, As RAM nodes don't have to write to disc as much as disc nodes, they can perform better.

As stated on rabbitmq configuration.

However, note that since persistent queue data is always stored on disc, the performance improvements will affect only resource management (e.g. adding/removing queues, exchanges, or vhosts), but not publishing or consuming speed.

We need to expose the cluster_node_type to be defined by the user.

Tags: openstack sts
Changed in rabbitmq-server (Juju Charms Collection):
importance: Undecided → Medium
assignee: nobody → Jorge Niedbalski (niedbalski)
Felipe Reyes (freyes)
tags: added: cts openstack sts
tags: removed: cts
James Page (james-page)
summary: - Allow ram clusters, by exposing cluster_node_type
+ feature: Allow ram clusters, by exposing cluster_node_type
Changed in rabbitmq-server (Juju Charms Collection):
status: New → Triaged
importance: Medium → Wishlist
James Page (james-page)
Changed in charm-rabbitmq-server:
assignee: nobody → Jorge Niedbalski (niedbalski)
importance: Undecided → Wishlist
status: New → Triaged
Changed in rabbitmq-server (Juju Charms Collection):
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.