-
Notifications
You must be signed in to change notification settings - Fork 51
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
Getting response for single subscription when multiple subscriptions are requested through config file with ONCE mode #382
Comments
This should be solved in v0.36.1, please give it a try. |
Hi @karimra, Instead of "continue" in the pkg/app/gnmi_client_subscribe.go (line 292), "continue OUTER" is working. |
That tells me the server you are testing this against is not closing the stream after sending a sync_update: true |
I tried closing stream by returning nil, and gnmic is sending next subscription but the gnmi-server is not receiving the next subscribe request (may be because stream is closed). |
Each subscription should start its own stream. Are you defining multiple subscriptions or a single one with multiple paths in your config file ? |
I am defining multiple subscriptions.
Gnmic is sending the request but there is nothing happening on server side.
…On Sat, Mar 9, 2024 at 2:35 PM Karim Radhouani ***@***.***> wrote:
Each subscription should start its own stream. Are you defining multiple
subscriptions or a single one with multiple paths in your config file ?
—
Reply to this email directly, view it on GitHub
<#382 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AZHYG55ABRTZ3AVBNQPV2STYXOFDBAVCNFSM6AAAAABD3DUE4OVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSOBWHE4TQMRZGY>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
.
|
While sending a subscribe request with multiple subscriptions through the config file, only one subscription is sent to the gnmi-server, and when response received, the rpc is closed. Hence, the other subscription from the input config file is never sent to the gnmi-server.
The text was updated successfully, but these errors were encountered: