-
Notifications
You must be signed in to change notification settings - Fork 775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Service Bus] Max time of message lock duration #470
Comments
I'm not sure about that. Messages are received and processed by some sort of client. So you can extend the lock for hours and hours. It's not guaranteed that renewing will work all the time as this is not a server-side operation. @EldertGrootenboer might help here a bit more. PS: if you want a simple service like SQS, Azure Storage Queues is the equivalent and can lock the message for a custom time. But ASQ is not as nice as ASB 🙂 |
Hi @SeanFeldman |
As Sean mentioned, you should be able to extend the lock on the same client you use to receive the message. If this doesn't work for you, can you explain a bit more about the process you are using? |
@EldertGrootenboer Before Apiserver build on AWS and AWS SQS had a ticket after receiving the message from SQS, using this ticket can delete the message anywhere and AWS SQS can set the lock duration longer than 5 minutes. Now we change the API server to Azure and use the service bus. In another word we want configure the server bus max lock duration is 15 minutes, and service side auto-renew to extend the lock duration from 5 minutes to 15 minutes, and do not need client to keep renew after review the message |
@DzcleisureCN we are working on a new feature (timelines for when this will be released are not available yet) which will remove the need to extend the lock, however this will still expect the client to keep the connection open. It can recover from connection loss while retaining the message state, but we do expect the client to keep the connection open in general, or to reconnect as soon as possible. |
@EldertGrootenboer |
@DzcleisureCN ASB is not the same as SQS. If you're looking for an SQS-like service, ASQ (Azure Storage Queues) is what you need. Not to be rude but this has already been pointed out earlier. Perhaps taking time to read up on ASQ vs ASB would help to cut down the number of questions that have been answered and documented. Cheers! |
@SeanFeldman |
ASB is a long-polling service. That's how it's designed. ASQ and SQS are HTTP-based services and do not keep a connection. Instead, those services poll for messages. |
Thank you for your feedback on this item. We are currently actively working on this feature, however we don't have a timeline to share yet around its release. |
We have brought this item in our current planning, and should be able to provide an update in the coming months. |
Description
As AWS(SQS) Max time of the message lock duration is more than 2 hours but service bus is only 5 minutes.
When we want to transfer from SQS to the service bus it is hard.
As I know service bus can auto-renew but this needs a client base receiver, but usually the process message and receive message is not a client, just use the ticket to process, it needs a service bus auto-renew to enlarge the message lock duration
Actual Behavior
Expected Behavior
The text was updated successfully, but these errors were encountered: