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

fix: fetches nssf uri even if already cached #138

Merged
merged 1 commit into from
Nov 23, 2023
Merged

fix: fetches nssf uri even if already cached #138

merged 1 commit into from
Nov 23, 2023

Conversation

gruyaume
Copy link
Contributor

Description

This PR makes it so that the SelectSmf function retrieves SearchNssfNSSelectionInstance even if there already is a stored value for the NSSF URI. This fixes an issue where the NSSF uri was only stored once on AMF startup and never retrieved again. This was a problem in cases where the NSSF crashed and its IP changed.

Fixes #133

}
// TODO: Set a timeout of NSSF Selection or will starvation here
for {
if err := SearchNssfNSSelectionInstance(ue, nrfUri, models.NfType_NSSF,
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Something to be done if not already available. NRF results are cached internally. We should see if we can cache this result as well. that code is part of NRF repo. It helps in performance. Also upon any failure in NRF cache should be refreshed.

@thakurajayL thakurajayL merged commit ec4f887 into omec-project:master Nov 23, 2023
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

AMF uses old NSSF address after NSSF IP changed
2 participants