synchronous pull pubsub node.js
up vote
0
down vote
favorite
I have a cloud function which is doing a synchronous pull from a pubsub subscription. the request is configured using the returnImmediately flag set to true so that we do not wait for pubsub messages to be present in the queue.
const request = {
subscription: formattedName,
maxMessages: maxMessages,
returnImmediately: true,
};
...
client.pull(request)
...
When there are some messages pending, the request returns very fast ( 100ms ) but when there is no messages in the queue, the call hangs for about 1.5 second before returning the empty array of messages.
as I am in a cloud function, I am not sure asynchronous pull is possible.
how could I get rid of this 1.5 s delay and get the pull(request) returns immediately when there is no pending messages ? it would feel very natural that a synchronous pull() with returnImmediately set to true, returns immediately
google-cloud-functions
google-cloud-pubsub edited Nov 19 at 21:20
Doug Stevenson
66.5k87997
asked Nov 19 at 21:12
amg0
61
add a comment |
up vote
0
down vote
favorite
I have a cloud function which is doing a synchronous pull from a pubsub subscription. the request is configured using the returnImmediately flag set to true so that we do not wait for pubsub messages to be present in the queue.
const request = {
subscription: formattedName,
maxMessages: maxMessages,
returnImmediately: true,
};
...
client.pull(request)
...
When there are some messages pending, the request returns very fast ( 100ms ) but when there is no messages in the queue, the call hangs for about 1.5 second before returning the empty array of messages.
as I am in a cloud function, I am not sure asynchronous pull is possible.
how could I get rid of this 1.5 s delay and get the pull(request) returns immediately when there is no pending messages ? it would feel very natural that a synchronous pull() with returnImmediately set to true, returns immediately
google-cloud-functions
google-cloud-pubsub edited Nov 19 at 21:20
Doug Stevenson
66.5k87997
asked Nov 19 at 21:12
amg0
61
Synchronous pubusb pull in Cloud Functions is not a good idea for many reasons. Instead, you should write a pubsub trigger to arrange for your code to run on each message. cloud.google.com/functions/docs/calling/pubsub
– Doug Stevenson
Nov 19 at 21:21
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a cloud function which is doing a synchronous pull from a pubsub subscription. the request is configured using the returnImmediately flag set to true so that we do not wait for pubsub messages to be present in the queue.
const request = {
subscription: formattedName,
maxMessages: maxMessages,
returnImmediately: true,
};
...
client.pull(request)
...
When there are some messages pending, the request returns very fast ( 100ms ) but when there is no messages in the queue, the call hangs for about 1.5 second before returning the empty array of messages.
as I am in a cloud function, I am not sure asynchronous pull is possible.
how could I get rid of this 1.5 s delay and get the pull(request) returns immediately when there is no pending messages ? it would feel very natural that a synchronous pull() with returnImmediately set to true, returns immediately
google-cloud-functions
google-cloud-pubsub edited Nov 19 at 21:20
Doug Stevenson
66.5k87997
asked Nov 19 at 21:12
amg0
61
I have a cloud function which is doing a synchronous pull from a pubsub subscription. the request is configured using the returnImmediately flag set to true so that we do not wait for pubsub messages to be present in the queue.
const request = {
subscription: formattedName,
maxMessages: maxMessages,
returnImmediately: true,
};
...
client.pull(request)
...
When there are some messages pending, the request returns very fast ( 100ms ) but when there is no messages in the queue, the call hangs for about 1.5 second before returning the empty array of messages.
as I am in a cloud function, I am not sure asynchronous pull is possible.
how could I get rid of this 1.5 s delay and get the pull(request) returns immediately when there is no pending messages ? it would feel very natural that a synchronous pull() with returnImmediately set to true, returns immediately
google-cloud-functions
google-cloud-pubsub google-cloud-functions
google-cloud-pubsub edited Nov 19 at 21:20
Doug Stevenson
66.5k87997
asked Nov 19 at 21:12
amg0
61
edited Nov 19 at 21:20
Doug Stevenson
66.5k87997
asked Nov 19 at 21:12
amg0
61
edited Nov 19 at 21:20
Doug Stevenson
66.5k87997
edited Nov 19 at 21:20
Doug Stevenson
66.5k87997
edited Nov 19 at 21:20
Doug Stevenson
66.5k87997
66.5k87997
asked Nov 19 at 21:12
amg0
61
asked Nov 19 at 21:12
amg0
61
asked Nov 19 at 21:12
amg0
61
61
Synchronous pubusb pull in Cloud Functions is not a good idea for many reasons. Instead, you should write a pubsub trigger to arrange for your code to run on each message. cloud.google.com/functions/docs/calling/pubsub
– Doug Stevenson
Nov 19 at 21:21
add a comment |
Synchronous pubusb pull in Cloud Functions is not a good idea for many reasons. Instead, you should write a pubsub trigger to arrange for your code to run on each message. cloud.google.com/functions/docs/calling/pubsub
– Doug Stevenson
Nov 19 at 21:21
Synchronous pubusb pull in Cloud Functions is not a good idea for many reasons. Instead, you should write a pubsub trigger to arrange for your code to run on each message. cloud.google.com/functions/docs/calling/pubsub
– Doug Stevenson
Nov 19 at 21:21
Synchronous pubusb pull in Cloud Functions is not a good idea for many reasons. Instead, you should write a pubsub trigger to arrange for your code to run on each message. cloud.google.com/functions/docs/calling/pubsub
– Doug Stevenson
Nov 19 at 21:21
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
As @DougStevenson pointed, you should write a Cloud Function to be triggered when there is a new message published in your topic, you can follow this tutorial, then you'll have a very fast response without any delay.
answered Nov 21 at 15:17
Alex Riquelme
40218
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
As @DougStevenson pointed, you should write a Cloud Function to be triggered when there is a new message published in your topic, you can follow this tutorial, then you'll have a very fast response without any delay.
answered Nov 21 at 15:17
Alex Riquelme
40218
add a comment |
up vote
0
down vote
As @DougStevenson pointed, you should write a Cloud Function to be triggered when there is a new message published in your topic, you can follow this tutorial, then you'll have a very fast response without any delay.
answered Nov 21 at 15:17
Alex Riquelme
40218
add a comment |
up vote
0
down vote
up vote
0
down vote
As @DougStevenson pointed, you should write a Cloud Function to be triggered when there is a new message published in your topic, you can follow this tutorial, then you'll have a very fast response without any delay.
answered Nov 21 at 15:17
Alex Riquelme
40218
As @DougStevenson pointed, you should write a Cloud Function to be triggered when there is a new message published in your topic, you can follow this tutorial, then you'll have a very fast response without any delay.
answered Nov 21 at 15:17
Alex Riquelme
40218
answered Nov 21 at 15:17
Alex Riquelme
40218
answered Nov 21 at 15:17
Alex Riquelme
40218
answered Nov 21 at 15:17
Alex Riquelme
40218
40218
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53382708%2fsynchronous-pull-pubsub-node-js%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Synchronous pubusb pull in Cloud Functions is not a good idea for many reasons. Instead, you should write a pubsub trigger to arrange for your code to run on each message. cloud.google.com/functions/docs/calling/pubsub
– Doug Stevenson
Nov 19 at 21:21