-
Notifications
You must be signed in to change notification settings - Fork 16
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
fix: observe GRPC client #135
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
Signed-off-by: gatici <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that changes are not consistent across the different NFs (in some NFs the updateConfig
is in service/init.go
like this in NF/PR and in other NFs, the same function goes in factory/factory.go
). Would this be a good time to make the change consistent across all NFs?
I will move the implementation to under service/init. |
fbdde66
to
26e1312
Compare
Signed-off-by: gatici <[email protected]>
26e1312
to
4fa3dfc
Compare
Signed-off-by: gatici <[email protected]>
@gatici do not forget to rebase your branch |
This PR aims to solve GPRC client connection issues which appears when GPRC server (webconsole) is restarted.
If the Webconsole is restarted, other modules loses the GRPC connection to Webconsole
They tries to connect again for hours with no success.
2024-09-26T11:32:10.014Z [smf] 2024-09-26T11:32:10Z [ERRO][Config5g][GRPC] Connectivity status idle, trying to connect again
NF observes the GRPC client availability and connection status in an infinite loop.
If the connection is ready it does nothing. If GRPC client does not exist, it creates new client. If GRPC client connection is not ready, it closes the existing client and creates another client.
Only one GRPC client exists for any time slot.