Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consumer only reads the number of messages in receiveQueueSize #71

Closed
sOfekS opened this issue Nov 11, 2021 · 1 comment · Fixed by #74
Closed

Consumer only reads the number of messages in receiveQueueSize #71

sOfekS opened this issue Nov 11, 2021 · 1 comment · Fixed by #74
Assignees
Labels
bug Something isn't working

Comments

@sOfekS
Copy link
Collaborator

sOfekS commented Nov 11, 2021

Describe the bug
Consumer only gets the number of messages in receiveQueueSize and then stops reading.

Reproduce
Please provide reproduce, For example:

  1. Run a producer that continuously produces messages to a topic
  2. Run a consumer that subscribes to that topic and logs each topic offset
  3. After the consumer has consumed receiveQueueSize messages, it stops.
    Expected behavior
    I expect it to read that number of messages as a sort of batch (only that amount can fit in the queue at once) but to still keep reading after reaching that amount.

Observed behavior
After the consumer has consumed receiveQueueSize messages, it just stops consuming messages.

Environment:

  • OS: CentOS 7.8
  • PulsarFlex version 1.0.1-beta.4
  • Pulsar version 2.8.1
  • NodeJS version 13.1.0

Additional context

@galrose galrose added the bug Something isn't working label Nov 13, 2021
@galrose galrose self-assigned this Nov 16, 2021
@galrose galrose mentioned this issue Nov 16, 2021
@sOfekS sOfekS closed this as completed Nov 16, 2021
@sOfekS
Copy link
Collaborator Author

sOfekS commented Nov 16, 2021

Closing. The issue was Node version under v14, now working with v16.13.0 and it works.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants