MDEXP-919 - 504 Gateway Timeout error when export deleted marc bib records from Member tenant on ECS Sprint testing environment#704
Merged
Conversation
(cherry picked from commit 2db280d)
# Conflicts: # NEWS.md # pom.xml
kjain110
approved these changes
May 20, 2026
siarhei-charniak
approved these changes
May 20, 2026
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
MDEXP-919 - 504 Gateway Timeout error when export deleted marc bib records from Member tenant on ECS Sprint testing environment
Purpose
Remove non-deleted shared MARC records from the response in member tenant without timeout 504 error after 1 minute.
Approach
Use /source-storage/source-records?idType=INSTANCE with all found deleted record ids to check leader in the central tenant.
TODOS and Open Questions
Learning
Pre-Merge Checklist
Before merging this PR, please go through the following list and take appropriate actions.
Does this PR meet or exceed the expected quality standards?
Does this introduce breaking changes?
If there are breaking changes, please STOP and consider the following:
Ideally all of the PRs involved in breaking changes would be merged in the same day to avoid breaking the folio-testing environment. Communication is paramount if that is to be achieved, especially as the number of intermodule and inter-team dependencies increase.
While it's helpful for reviewers to help identify potential problems, ensuring that it's safe to merge is ultimately the responsibility of the PR assignee.