How can I improve RabbitMQ performance without guessing?
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
A performance change should improve the measured workload without sacrificing correctness or wasting capacity. Which measurements and bottlenecks should be considered first?
I have installed rabbitmq using helm chart on a kubernetes cluster. The rabbitmq pod keeps restarting. On inspecting the pod logs I get the below error 2020-02-26 04:42:31.582 [warning] <0.314.0> Error while waiting for Mnesia tables: {timeout_waiting_for_tables,[rabbit_durable_queue]} 2020-02-26 04:42:31.582 [info] <0.314.0> Waiting for Mnesia t
A failure needs to be narrowed down before settings are changed or operations retried. Which evidence best separates application errors from environment and dependency problems?
Configuration must be available to the application without exposing credentials in source control, logs or browser code. What belongs in the runtime and which access controls matter?