MetaDataUpdate ends up with unhandledRejection

[spirin22]

First of all, I want to thank you for the amazing work on this project! I have an issue and would appreciate your opinion.

My setup:

RabbitMQ: 3.11.20 (cluster with 3 nodes behind k8s service, unfortunately can't upgrade it yet)
rabbitmq-stream-js-client: 0.6.0
Node.js: 22.13.1

I often observe metadata_update in my staging environment with code 0x06 (Stream not available). Unfortunately, I don't know the reason yet, and looking at logs didn't help me to understand it. My rabbitmq nodes don't have any errors or reloads at the moment of metadata_update and write only these info logs related to the stream I receive the metadata_update for:

info rabbitmq-main-server-2 Stream: test-stream-2_1739894330824592080 will use /bitnami/rabbitmq/mnesia/rabbit@rabbitmq-main-server-2.rabbitmq-main-nodes.rabbitmq/stream/test-stream-2_1739894330824592080 for osiris log data directory

info rabbitmq-main-server-2 test-stream-2_1739894330824592080 [osiris_replica:handle_continue/2] osiris replica starting in epoch 3, next offset 8624, tail info {8624,{2,8623,1741903053199}}

info rabbitmq-main-server-1 test-stream-2_1739894330824592080: starting osiris replica reader at offset 8624

info rabbitmq-main-server-2 rabbit_stream_coordinator: test-stream-2_1739894330824592080: replica started on rabbit@rabbitmq-main-server-2.rabbitmq-main-nodes.rabbitmq in 3 pid <0.2410.11>

This is followed by consumer close and therabbitmq-stream-js-client calls Connection.closeConsumer(consumer.extendedId). The request gets an unsuccessful response and the lib throws code 4 - Subscription ID does not exist error. That rejection of closeConsumer promise ends up unhandled as the lib doesn't handle it and doesn't expose any way to handle it on my side.

I would like to contribute and add an error event to listeners if you support this. Also, I would really appreciate any guidance on how to debug the issue I have.

[Gsantomaggio]

Hi @spirin22,
Metadata update happens when something changes on the stream topology, for example:

• RabbitMQ Node restart
• Add or remove replicas to the stream
• Delete a stream

About the message:

• StreamNotAvailable is a server-side error: Stream exists but is not available for the producer and consumer

Please check this presentation about the stream states https://docs.google.com/presentation/d/111PccBLRGb-RNpYEKeIm2MQvdky-fXrQ/edit#slide=id.p10

[spirin22]

Thank you so much for your prompt response, @Gsantomaggio!

I’ve already found that presentation in the .NET client docs. Unfortunately, the logs from my RabbitMQ cluster don’t show any issues.

I’ll try to push for upgrading RabbitMQ in my company. However, what do you think about the errors thrown by the library with no way to handle them? I could contribute an error listener instead of having them thrown.

[Gsantomaggio]

I am sorry, but I don't know how the client handles metadata update. We will let you know.

[spirin22]

fyi stack trace of my error is:

• throw new Error(Unsubscribe command returned error with code ${res.code} - ${errorMessageOf(res.code)}) with code 4 - Subscription ID does not exist
• await this.closeConsumer(consumer.extendedId)