Behaviour of NACKED message in PubSub
In the documentation we can find this:
How to use workload identity with GCP pubsub python client?
I am trying to use google-cloud-pubsub python client. All of the examples I have seen so far only seem to use key.json file for a specific service account. Is there a way to use GCP workload identity with this client library?
504 Deadline Exceeded in google pub/sub python
from google.cloud import pubsub_v1 if __name__ == ‘__main__’: publisher = pubsub_v1.PublisherClient( credentials=”/Users/quang/.config/gcloud/application_default_credentials.json” ) a = publisher.list_topics( timeout=10, ) print(a) Error: raise exceptions.from_grpc_error(exc) from exc google.api_core.exceptions.DeadlineExceeded: 504 Deadline Exceeded python 3.12.3 google-api-core 2.19.0 google-api-python-client 2.135.0 google-auth 2.29.0 google-auth-httplib2 0.2.0 google-cloud-core 2.4.1 google-cloud-firestore 2.16.0 google-cloud-pubsub 2.13.12 I am using Google Pub/Sub for my project. I have followed […]
Push Subscription with long-running tasks
I have tasks that can be completed in ~3 mins. Cloud Run offers 600 seconds as a maximum timeout, so this is not an issue. We decided to use Cloud Run + Pub/Sub with push subscription.
DeadlineExceeded Exception while publishing message to GCP Pub sub from Java Springboot app
In Java Springboot app, i’m publishing message to GCP Pub Sub and it is getting failed sometimes with DeadlineExceeded exception. Can someone please advise me on best retry approach.
GCP PubSub asynch Publish, long delays in running callback
We are running Microservices on GKE and we subscribe and publish messages to PubSub asynchronously. We are seeing huge delays executing the callbacks where the P99 is in the order of 6-10s irrespective of the load.
Does subscription ack setting in GCP Pub Sub are automatically overriden by the client library for pull subscriptions?
We are using GCP Pub Sub client library (com.google.cloud.pubsub.v1) to process the messages from a subscription.
The pull subscription has the default ACK deadline of 10 seconds.
GCP Pub-sub push subscription with message ordering, expected failure behavior
I have a push subscription set up with message ordering enabled. I also have a dead-letter topic/subscription set up. I published 5 messages with the same ordering key, and message #2 fails.