google-cloud-node: subscription.on message wasn't received of messagActually unrelated failures, but we should bump this anyway.es after 10 mins or more.

OS: Debian
Node.js version: 8.4.0
npm version: 5.4.0
google-cloud-node version: 0.56.0
@google-cloud/pubsub version: 0.14.0

Steps to reproduce

const pubsub = require ( '@google-cloud/pubsub' )( connectOption )

const subscription = pubsub.topic ( topicName ).subscription ( subScription )

subscription.on ('message', message => {
    message.ack()
    ....
})

subscription.once('error', err => {
    ....
})

I received all un-received messages when I restart it. I checked the connectionPool object when it have not received message: connectionPool.isPaused [false] connectionPool.isOpen [true] connectionPool.connections [5]

Thank you.

About this issue

Original URL
State: closed
Created 7 years ago
Reactions: 3
Comments: 28 (13 by maintainers)

Most upvoted comments

This is definitely a result of moving towards the new streaming API, I’m working on resolving this issue, but in the mean time I suggest downgrading to 0.13. I’ll update this issue once it’s been resolved.

callmehiphop on Sep 23, 2017

will this be addressed by #2716

I believe it will!

callmehiphop on Nov 3, 2017

OS: Debian
Node.js version: 8.7.0
npm version: 5.5.1
@google-cloud/pubsub version: 0.14.5

Steps to reproduce

const pubsub = require ( '@google-cloud/pubsub' )( connectOption )

const listenSub = () => {
    let subscription = pubsub.topic ( topicName ).subscription ( subScription )
    subscription.on ( 'message', message => {
        message.ack()
        ....
   })

    //        each 10 mins restart
    const tt = setTimeout (() => {
	return subscription.close().then(() => {
	    listenPubSubMaster = null
	    return listenSub ()
    }, 600000 )
}

listenSub()

I did make new subscription each 10 mins. But looks the @google-cloud/pubsub did not release memory when pubsub exit with subscription.close().

pubsub

CoNETProject on Oct 16, 2017

We see a similar behavior, although it takes a few hours. Eventually the subscription stops processing new messages and we have to restart the subscription. This only started after upgrading to 0.14.

caseyduquettesc on Sep 18, 2017