Explanation of how Streaming CLI tools work

59 views
Skip to first unread message

Ricard Siliuk

unread,
Jul 26, 2022, 7:46:54 AM7/26/22
to rabbitmq-users

Hi,

Is there anyone who could explain a few things regarding `rabbitmq-streams` cli tool (code https://github.com/rabbitmq/rabbitmq-server/blob/master/deps/rabbitmq_cli/lib/rabbitmq/cli/streams/commands/stream_status_command.ex)?

In particular, I'd like to know whether RPC it's accessing is available as an HTTP API endpoint, or is there a way to query for that info without `rabbitmq-streams` tool.

Maybe just pointing me to where all endpoints are defined is sufficient?

Regards,
Ricard

Arnaud Cogoluègnes

unread,
Jul 26, 2022, 8:26:06 AM7/26/22
to rabbitmq-users
Such information is not available with the HTTP API. There are some stream-related HTTP endpoints as part of the stream management plugin, but they are more connection-/publisher-/consumer-oriented.

It should not be a big deal to add the fields of the stream_status command to the JSON document of the /api/queues/{vhost}/{name} endpoint though.

What is your use case?

Ricard Siliuk

unread,
Jul 26, 2022, 8:31:55 AM7/26/22
to rabbitmq-users
We had observed a bug where stream would go out of sync between primary and secondary nodes (discussed in RabbitMQ Slack). Easiest way to see this was by running `rabbitmq-streams` command and seeing that message counts on nodes were wildly off (ofc, one can also observe missing acks on the client). We'd like to monitor that stream is in sync across nodes but don't want to write parser for output of that command :) 

Arnaud Cogoluègnes

unread,
Jul 26, 2022, 8:49:25 AM7/26/22
to rabbitmq-users
Can you provide the link to the thread on RabbitMQ Slack?

Ricard Siliuk

unread,
Jul 26, 2022, 8:51:40 AM7/26/22
to rabbitmq-users

Arnaud Cogoluègnes

unread,
Jul 26, 2022, 9:40:05 AM7/26/22
to rabbitmq-users
We provided a fix [1] for the problem diagnosed in that Slack thread. It did not make it to 3.10.6 unfortunately, because we wanted to do more testing on the stream storage library [2], but it should be in 3.10.7.

Ricard Siliuk

unread,
Jul 26, 2022, 10:01:51 AM7/26/22
to rabbitm...@googlegroups.com

Oh, I know that the solution is on the way J I’d still like to monitor for that issue just to be safe, if that’s possible. If not, I can live with it, just wanted to know if I was missing a way to see into stream info!

--
You received this message because you are subscribed to a topic in the Google Groups "rabbitmq-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/rabbitmq-users/y58YSl16ZkQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to rabbitmq-user...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/rabbitmq-users/a8b48bf6-dc98-416f-8526-702b3aff28f9n%40googlegroups.com.


Šioje žinutėje esanti informacija gali būti konfidenciali. Jeigu šią žinutę gavote per klaidą, prašome grąžinti ją siuntėjui atsakant į gautą laišką ir iškart ištrinkite žinutę iš Jūsų sistemos nekopijuojant, neplatinant ir neišsisaugant jos.
Nors esame įsitikinę, kad ši žinutė ir prie jos esantys priedai nėra užkrėsti virusais ar kitaip pažeisti, dėl ko galėtų būti paveiktas kompiuteris ar IT sistema, kurioje žinutė gauta ir skaitoma, adresatas atidarydamas failą prisiima riziką. Mes neatsakome už nuostolius ar žalą, galinčius atsirasti dėl šios žinutės gavimo ar kitokio naudojimo.
_______________
Please note that this message may contain confidential information. If you have received this message by mistake, please inform the sender of the mistake by sending a reply, then delete the message from your system without making, distributing or retaining any copies of it. Although we believe that the message and any attachments are free from viruses and other errors that might affect the computer or IT system where it is received and read, the recipient opens the message at his or her own risk. We assume no responsibility for any loss or damage arising from the receipt or use of this message.
Reply all
Reply to author
Forward
0 new messages