-
Notifications
You must be signed in to change notification settings - Fork 781
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
Break message lock #639
Comments
This can be done by abandoning the message, isn't it? |
Abandoning works if your code is the receiving code and has the message's lease. Otherwise, it doesn't. |
Thank you for your explanation! We will add this to the backlog as a feature request. We are not considering this short-term, but if more people are interested in this please upvote, and we will keep tracking this. |
It's ok. I've got about 20 years until retirement 😉 |
Thank you for your feedback on this item, it helps us in our efforts to continuously prioritize the different requests we get from all our various feedback channels. We have added this feature in our backlog, however we currently don't have an ETA on when development might start on this. For now, to help us give this the right priority, it would be helpful to see others vote and support this feature, as well as explain their scenarios. |
This feature in our backlog, however we currently don't have an ETA on when development might start on this. For now, to help us give this the right priority, it would be helpful to see others vote and support this feature, as well as explain their scenarios. |
Currently, a message locked cannot be unlocked until the lease runs out. If the lock duration is set to 5 minutes, it will take up to 5 minutes to unlock the message. When developing, often there's a need to retry the same message while debugging. The only hacky workaround today to avoid wasting time on waiting is modifying one of the queue properties to reset the lock. An ability to break a message lock by message sequence number would be beneficial.
cc @EldertGrootenboer
The text was updated successfully, but these errors were encountered: