-
Notifications
You must be signed in to change notification settings - Fork 1
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
RAS-1228: Bug: Party service workers getting 139 SIGSEGV errors and restarting #433
base: main
Are you sure you want to change the base?
RAS-1228: Bug: Party service workers getting 139 SIGSEGV errors and restarting #433
Conversation
/deploy scorfs |
Deploying to dev cluster with following parameters:
|
/deploy scorfs |
Deploying to dev cluster with following parameters:
|
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.
Not sure I like the naming of this. But I couldn't think what would be a good name for this.
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.
Due to the retrieval of the enrolment DTO, I had to extract these functions out of the unified_business_party_functions.py
@@ -79,6 +79,13 @@ def get_business_by_ref(ref): | |||
return jsonify(business) | |||
|
|||
|
|||
@business_view.route("/businesses/ref/reporting-unit-only/<ref>", methods=["GET"]) |
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.
Not keen on the naming of this endpoint. Any ideas?
What and why?
There have been a lot of 139 SIGSEGV errors and restarting by the service. The main culprit appears to be the way the calls are being handled and data retrieval of the associations. Due to the complexity of the interconnections between the services, it wasn't possible to separate the calls to associations. There needs to be further investigation into what services are calling the endpoints and whether they actually need the associations.
This code change extracts out the various data dictionaries used by the business and party into one unified dictionary.
A new endpoint has been added that when called will only not bring back associations. I think this is the way to goto to help minimise the amount of calls being made.
How to test?
Jira
https://jira.ons.gov.uk/browse/RAS-1228