Azure: How to move messages from poison queue to back to main queue?

前端 未结 7 1793
慢半拍i
慢半拍i 2020-12-30 06:57

I\'m wondering if there is a tool or lib that can move messages between queues? Currently, i\'m doing something like below

public static void ProcessQueueMes         


        
相关标签:
7条回答
  • 2020-12-30 07:30

    To anyone coming here looking for a Node equivalent of @MitchWheats answer using an Azure Function.

    import AzureStorage from 'azure-storage'
    import { Context, HttpRequest } from '@azure/functions'
    import util from 'util'
    
    const queueService = AzureStorage.createQueueService()
    queueService.messageEncoder = new AzureStorage.QueueMessageEncoder.TextBase64QueueMessageEncoder()
    
    const deleteMessage = util.promisify(queueService.deleteMessage).bind(queueService)
    const createMessage = util.promisify(queueService.createMessage).bind(queueService)
    const getMessage = util.promisify(queueService.getMessage).bind(queueService)
    
    export async function run (context: Context, req: HttpRequest): Promise<void> {
      try {
        const poisonQueue = (req.query.queue || (req.body && req.body.queue));
        const targetQueue = poisonQueue.split('-')[0]
    
        let count = 0
    
        while (true) {
          const message = await getMessage(poisonQueue)
          if (!message) { break; }
          if (message.messageText && message.messageId && message.popReceipt) {
            await createMessage(targetQueue, message.messageText)
            await deleteMessage(poisonQueue, message.messageId, message.popReceipt)
          }
          count++
        }
    
        context.res = {
          body: `Replayed ${count} messages from ${poisonQueue} on ${targetQueue}`
        };
      } catch (e) {
        context.res = { status: 500 }
      }
    }
    

    To use the function you need to you provide connection information for the storage account used for your storage queues. This is provided as environment variables. Either you provide AZURE_STORAGE_ACCOUNT and AZURE_STORAGE_ACCESS_KEY, or AZURE_STORAGE_CONNECTION_STRING. More on this is available in the Azure Storage SDK docs.

    Also wrote a few lines about it in this Medium article

    0 讨论(0)
  • 2020-12-30 07:33

    As Mikael Eliasson noted, the code in IGx89 answer is broken because

    AddMessageAsync will overwrite some info on the message and then DeleteMessagAsync will give a 404. The better solution is to copy the values into a new message for AddMessageAsync

    Please see enhanced version of RetryPoisonMesssages with an ability to specify only list of messages(instead of all in a queue) and allow to copy messages instead of move them. It also logs success/failure for each message.

    /// <param name="storageAccountString"></param>
    /// <param name="queuename"></param>
    /// <param name="idsToMove">If not null, only messages with listed IDs will be moved/copied</param>
    /// <param name="deleteFromPoisonQueue">if false,  messages will be copied; if true, they will be moved</param>
    /// <returns></returns>
    private static async Task<int> RetryPoisonMesssages(string storageAccountString, string queuename, string[] idsToMove=null, bool deleteFromPoisonQueue=false)
    {
        var targetqueue = GetCloudQueueRef(storageAccountString, queuename);
        var poisonQueueName = queuename + "-poison";
        var poisonqueue = GetCloudQueueRef(storageAccountString, poisonQueueName);
    
        var count = 0;
        while (true)
        {
            var msg = await poisonqueue.GetMessageAsync();
            if (msg == null)
            {
                Console.WriteLine("No more messages in a queue " + poisonQueueName);
                break;
            }
    
            string action = "";
            try
            {
                if (idsToMove == null || idsToMove.Contains(msg.Id))
                {
                    var msgToAdd = msg;
                    if (deleteFromPoisonQueue)
                    {
                        //The reason is that AddMessageAsync will overwrite some info on the message and then DeleteMessagAsync will give a 404.
                        //The better solution is to copy the values into a new message for AddMessageAsync 
                         msgToAdd = new CloudQueueMessage(msg.AsBytes);
                    }
    
                    action = "adding";
                    await targetqueue.AddMessageAsync(msgToAdd);
                    Console.WriteLine(action + " message ID " + msg.Id);
                    if (deleteFromPoisonQueue)
                    {
                        action = "deleting";
                        await poisonqueue.DeleteMessageAsync(msg);
                    }
                    Console.WriteLine(action + " message ID " + msg.Id);
                }
            }
            catch (Exception ex)
            {
                Console.WriteLine("Error encountered when "+ action + " " + ex.Message + " at message ID " + msg.Id);
            }
    
            count++;
        }
    
        return count;
    }
    
    0 讨论(0)
  • 2020-12-30 07:39

    Here's a python script you may find useful. You'll need to install azure-storage-queue

    queueService = QueueService(connection_string = "YOUR CONNECTION STRING")
    for queue in queueService.list_queues():
      if "poison" in queue.name:
        print(queue.name)
        targetQueueName = queue.name.replace("-poison", "")
        while queueService.peek_messages(queue.name):
          for message in queueService.get_messages(queue.name, 32):
            print(".", end="", flush=True)
            queueService.put_message(targetQueueName, message.content)
            queueService.delete_message(queue.name, message.id, message.pop_receipt)
    
    0 讨论(0)
  • 2020-12-30 07:40

    Essentially Azure Storage doesn't support moving messages from one queue to another. You would need to do this on your own.

    One way to implement moving the messages from one queue to another is by dequeuing the messages from the source queue (by calling GetMessages), read the contents of the message and then creating a new message in the target queue. This you can do via using Storage Client Library.

    One tool that comes to my mind for moving messages is Cerebrata Azure Management Studio. It has this functionality.

    As at (2018-09-11) version 1.4.1 of the Microsoft Azure Storage Explorer doesn't support moving queue messages.

    0 讨论(0)
  • 2020-12-30 07:44

    As at (2018-09-11) version 1.4.1 of the Microsoft Azure Storage Explorer doesn’t have the ability to move messages from one Azure queue to another.

    I blogged a simple solution to transfer poison messages back to the originating queue and thought it might save someone a few minutes. Obviously, you'll need to have fixed the error that caused the messages to end up in the poison message queue!

    You’ll need to add a NuGet package reference to Microsoft.NET.Sdk.Functions :

    using Microsoft.WindowsAzure.Storage;
    using Microsoft.WindowsAzure.Storage.Queue;
    
    void Main()
    {
        const string queuename = "MyQueueName";
    
        string storageAccountString = "xxxxxx";
    
        RetryPoisonMesssages(storageAccountString, queuename);
    }
    
    private static int RetryPoisonMesssages(string storageAccountString, string queuename)
    {
        CloudQueue targetqueue = GetCloudQueueRef(storageAccountString, queuename);
        CloudQueue poisonqueue = GetCloudQueueRef(storageAccountString, queuename + "-poison");
    
        int count = 0;
        while (true)
        {
            var msg = poisonqueue.GetMessage();
            if (msg == null)
                break;
    
            poisonqueue.DeleteMessage(msg);
            targetqueue.AddMessage(msg);
            count++;
        }
    
        return count;
    }
    
    private static CloudQueue GetCloudQueueRef(string storageAccountString, string queuename)
    {
        CloudStorageAccount storageAccount = CloudStorageAccount.Parse(storageAccountString);
        CloudQueueClient queueClient = storageAccount.CreateCloudQueueClient();
        CloudQueue queue = queueClient.GetQueueReference(queuename);
    
        return queue;
    }
    
    0 讨论(0)
  • 2020-12-30 07:46

    Here's an updated version of Mitch's answer, using the latest Microsoft.Azure.Storage.Queue package. Simply create a new .NET Console application, add the above-mentioned package to it, and replace the contents of Program.cs with the following:

    using Microsoft.Azure.Storage;
    using Microsoft.Azure.Storage.Queue;
    using System.Threading.Tasks;
    
    namespace PoisonMessageDequeuer
    {
        class Program
        {
            static async Task Main(string[] args)
            {
                const string queuename = "MyQueueName";
    
                string storageAccountString = "xxx";
    
                await RetryPoisonMesssages(storageAccountString, queuename);
            }
    
            private static async Task<int> RetryPoisonMesssages(string storageAccountString, string queuename)
            {
                var targetqueue = GetCloudQueueRef(storageAccountString, queuename);
                var poisonqueue = GetCloudQueueRef(storageAccountString, queuename + "-poison");
    
                var count = 0;
                while (true)
                {
                    var msg = await poisonqueue.GetMessageAsync();
                    if (msg == null)
                        break;
    
                    await poisonqueue.DeleteMessageAsync(msg);
                    await targetqueue.AddMessageAsync(msg);
                    
                    count++;
                }
    
                return count;
            }
    
            private static CloudQueue GetCloudQueueRef(string storageAccountString, string queuename)
            {
                var storageAccount = CloudStorageAccount.Parse(storageAccountString);
                var queueClient = storageAccount.CreateCloudQueueClient();
                var queue = queueClient.GetQueueReference(queuename);
    
                return queue;
            }
        }
    }
    

    It's still pretty slow if you're working with >1000 messages though, so I'd recommend looking into batch APIs for higher quantities.

    0 讨论(0)
提交回复
热议问题