Fix Critical Database Performance and Hibernate Issues #218
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR addresses the critical database performance bottlenecks and Hibernate stack overflow errors identified in the root cause analysis.
Issues Fixed
🔥 Critical Issues
deleteAllInBatchmethod causing 2.44% fault rate with native SQL query📊 Performance Improvements
CONN_MAX_AGE,MAX_CONNS,MIN_CONNSsettingsconnect_timeoutto 10 seconds with proper transaction isolationFiles Changed
pet_clinic_insurance_service/pet_clinic_insurance_service/settings.py- Database connection poolingspring-petclinic-customers-service/src/main/resources/application.yml- HTTP client timeoutsspring-petclinic-customers-service/.../OwnerRepository.java- Hibernate fix with native queryExpected Impact
Testing
Fixes the critical availability issues identified in the Application Signals investigation.