You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
This bug is the result of #1497 spike.
Update of 1 node with no replication to a few replicated nodes leads to data loss. Also no rabbitmqctl forget_cluster_node <node> executed during downscale, so it leads to some issues, such of removed node disk presence in cluster information.
To Reproduce
Steps to reproduce the behavior:
deploy 1 rabbitmq node with disabled clustering (default configuration)
create some entities: users/queues/vhosts (see More information part with useful commands)
seriva
changed the title
[BUG][RabbitMQ] Update of 1 node with no replication to a few replicated nodes leads to data loss
[BUG] Update of 1 node with no replication to a few replicated nodes leads to data loss
Apr 20, 2022
Describe the bug
This bug is the result of #1497 spike.
Update of 1 node with no replication to a few replicated nodes leads to data loss. Also no
rabbitmqctl forget_cluster_node <node>
executed during downscale, so it leads to some issues, such of removed node disk presence in cluster information.To Reproduce
Steps to reproduce the behavior:
More information
part with useful commands)Config files
count: 3
)Expected behavior
rabbitmqctl forget_cluster_node <node>
should be executed during downscale to be able avoid some results of [BUG] Disks are not removed after downscale of any Epiphany component (Azure) #1574Config files
Cloud Environment (please complete the following information):
Azure, but should also be tested with other providers.
Additional context
Found in version 0.7.1.
More information
Verification commands
DoD checklist
The text was updated successfully, but these errors were encountered: