简体   繁体   English

如何修改 GCP Pub/Sub 上推送订阅消息的确认截止日期?

[英]How to modify ack deadline for a push subscription message on GCP Pub/Sub?

I am trying to figure out how to modify the ack deadline for a push subscription message.我试图弄清楚如何修改推送订阅消息的确认截止日期。 The problem is, I don't have the ack Id which is a required argument for the modify_ack_deadline function.问题是,我没有 ack Id,它是modify_ack_deadline function 的必需参数。 The message which is being pushed to the endpoint doesn't seem to have the acknowledgement id in it.被推送到端点的消息似乎没有确认 ID。 So my question is, how do I get a hold of this acknowledgement id if it's even possible?所以我的问题是,如果可能的话,我如何获得这个确认ID?

Ref: https://googleapis.dev/python/pubsub/latest/pubsub/subscriber/api/client.html#google.cloud.pubsub_v1.subscriber.client.Client.modify_ack_deadline参考: https://googleapis.dev/python/pubsub/latest/pubsub/subscriber/api/client.html#google.cloud.pubsub_v1.subscriber.client.Client.modify_ack_deadline

There is no way to modify the ack deadline when using a push subscription.使用推送订阅时,无法修改确认截止日期。 The message must be acknowledged within the subscription's configured ack deadline.消息必须在订阅配置的确认期限内得到确认。 If extending the ack deadline is needed, the a pull subscription must be used.如果需要延长确认期限,则必须使用拉订阅。

暂无
暂无

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 即使将确认截止日期设置为 600 秒,Pub/Sub 也会在 10 秒后重新发送消息。 如何克服这个问题? - Pub/Sub re-sending message after 10 sec even setting ack deadline 600 sec. How to overcome this issue? Pub/Sub 测试:即使通过了 ack_deadline,客户端也会收到消息 - Pub/Sub testing: message received by client even when ack_deadline is passed Dataflow Pub/Sub 流作业卡住并不断修改消息的 ACK 截止日期 - Dataflow Pub/Sub streaming jobs get stuck and keep modifying ACK deadline of messages 发送到在创建订阅之前存在的主题的 GCP Pub/Sub 消息 - GCP Pub/Sub Messages sent to topic that existed before the subscription was created 将来自不同项目的服务帐户分配给 Pub/Sub 上的推送订阅 - Assign a service account from a different project to a push subscription on Pub/Sub GCP Pub/Sub,如果已有活动订阅,您能否在新订阅上重播旧消息 - GCP Pub/Sub, can you replay old messages on a new Subscription if there is already an active Subscription 如何使用 Terraform 配置 GCP 发布/订阅死信 - How to configure GCP pub/sub dead letter with Terraform 为什么 GCP Pub/Sub 消息具有重复的 message_id 和 publish_time 值? - Why do GCP Pub/Sub messages have duplicated message_id and publish_time values? Google Pub/Sub “订阅不能同时启用消息排序和配置死信策略。” - Google Pub/Sub "A subscription cannot have both message ordering enabled and a dead letter policy configured." BigQuery 表订阅的 Pub/Sub 主题 - Pub/Sub Topic to BigQuery Table Subscription
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM