pubsub triggered cloud function not ack the message, even after func executes successfully

Question

I have this simple python function where i am just taking the input from pubsub topic and then print it.

import base64,json

def hello_pubsub(event, context):
    """Triggered from a message on a Cloud Pub/Sub topic.
    Args:
         event (dict): Event payload.
         context (google.cloud.functions.Context): Metadata for the event.
    """
    pubsub_message = base64.b64decode(event['data'])
    data           = json.loads(pubsub_message)
    for i in data:
         for k,v in i.items():
              print(k,v)

If i had used the pubsub_v1 library, there i could do following.

subscriber = pubsub_v1.SubscriberClient()

def callback(message):
        message.ack()

subscriber.subscribe(subscription_path, callback=callback)

How do i ack the message in pubsub triggered function?

How many subscription do you have on your topic? How can you say that the message isn't acked? — guillaume blaquiere
i have one subscription on this topic. i can still pull the messages from the queue even after function successfully exits. "Function execution took 3346 ms, finished with status: 'ok'" — akrsha

guillaume blaquiere guillaume blaquiere · Accepted Answer · 2020-09-25T08:39:19

Following your latest message, I understood the (common) mistake. With Pubsub, you have

a topic, and the publishers can publish messages in it
(push or pull) subscriptions. All the messages published in the topic are duplicated in each subscription. The message queue belong to each subscription.

Now, if you look closely to your subscriptions on your topic, you will have at least 2.

The pull subscription that you have created.
A push subscription created automatically when you deployed your Cloud Function on the topic.

The messages of the push subscription is correctly processed and acknowledge. However those of pull subscription aren't, because the Cloud Function don't consume and acknowledge them; the subscription are independent.

So, your Cloud Function code is correct!

pubsub triggered cloud function not ack the message, even after func executes successfully

2 Answers