-
Notifications
You must be signed in to change notification settings - Fork 227
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
Should be possible to nack a message for delayed redelivery #255
Comments
I had this issue as well, but just add a delay to the nack, and increase concurrency. 😐 |
That's basically what we're doing now, but it does not scale well, at all. |
This has been closed with a commit by @JustinBeckwith but unless I am missing something it does not appear to be integrated, what is the status? |
@callmehiphop can you speak to this, we've released quite a few releases of the library since this this landed, is the option just not exposed to users? |
I understand that this was reverted but the need for this remains. Any plans? |
My understanding is that the PubSub team is aware that users want this functionality and they're planning something around it, but currently there's nothing on my radar. |
Are you referring to ordering, or to delayed retries? There are good reasons for delayed retries that have nothing to do with ordering, as evidenced by Google's on (very good!) recommendations on exponential backoff ... which PubSub doesn't seem to believe in? |
You can now configure a retry policy in your Cloud Pub/Sub subscription. Retry policy allows users to have per message exponential backoff in case of failures. More information can be found here. |
To save folks that come here and are about to ask the question I was going to of "how": #1029 From some UTSL: it looks like the basic answer is "use |
You should be able to configure the retry policy by way of the
(There are other metadata operations available too, try |
Environment details
@google-cloud/pubsub
version: currentSteps to reproduce
nack
ingThis is something I'd been looking for for my application, but also came across in #119 (comment)
The suggestion there of adding an optional delay parameter to the
nack
method looks like exactly the trick.Intending to file a PR for this unless I receive objections to the idea.
The text was updated successfully, but these errors were encountered: