-
Notifications
You must be signed in to change notification settings - Fork 21
Cluster node won't start after reboot when setup federated exchange queue #111
Comments
Duplicate of #109. |
Something in your environment results in plugin's defaults not being loaded. You can explicitly set the undefined value of [
{rabbitmq_federation, [
{pgroup_name_cluster_id, false}
]}
]. or upgrade to |
Looking at the log I have a good guess as to what may be going on here. This seems to be a yet another "definition import before plugins are activated" problem that 3.8.6 addressed for different reasons. See rabbitmq/rabbitmq-server#2384. |
Same result with |
@rerime the exception in the provided log snippet states that So I find it hard to believe that this scenario is realistic with |
@michaelklishin |
I cannot reproduce with
|
@michaelklishin
Log
|
@rerime which is rabbitmq/rabbitmq-server#2384, so you want to upgrade to |
Setup federation between two clusters
Add queue on hq-0 cluster A
Reboot node ha-0 on cluster A where federated queue is located, node won't start
Log
System
The text was updated successfully, but these errors were encountered: