Great questions, let's break this down step by step:

Short answer: No, you can't.

Once a queue is created on a specific RabbitMQ node, its node assignment is fixed. The queue's metadata and message data are stored directly on that node, and RabbitMQ doesn't support reassigning an existing queue to another node—either through the Management Console or command-line tools. Any attempt to "change" the node would essentially require recreating the queue elsewhere, since moving the underlying data isn't a built-in operation.

If you need to move queue data to another node, here are your practical options:

• Use mirrored queues: Set up queue mirroring to replicate the queue's messages to other nodes in the cluster. This doesn't move the original queue, but it makes the queue's data available on multiple nodes for redundancy and access.
• Export and reimport messages: Use tools like rabbitmqadmin or custom scripts to export messages from the original queue, create a new queue on your target node, then import the messages into the new queue. Note you'll need to update any producers/consumers to point to the new queue after this.

In a properly configured RabbitMQ cluster, clients connected to any node should be able to access queues on other nodes—this is one of the core features of clustering. If you can't read messages from the RabbitMQ1 queue while connected to RabbitMQ2, there's likely a configuration issue to troubleshoot first:

• Check if the cluster is fully connected: Ensure RabbitMQ1 and RabbitMQ2 are properly clustered and can communicate with each other (verify with rabbitmqctl cluster_status on either node).
• Verify permissions: Make sure the client user has the necessary permissions to access the queue across the cluster (check permissions in the Management Console under Admin > Users > Permissions).
• Check for network issues: Ensure there's no firewall or network rule blocking communication between the client's connected node (RabbitMQ2) and the queue's node (RabbitMQ1).

If you still want to switch the client's connection to RabbitMQ1 directly, that's straightforward—just update your client's connection configuration to point to RabbitMQ1's hostname or IP address instead of RabbitMQ2. There's no "setting" in RabbitMQ itself to change the connection node; this is controlled entirely by the client's connection parameters.

内容的提问来源于stack exchange，提问作者Jovana