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

[debug] Stable9.1 fed share lag test #26817

Closed
wants to merge 3 commits into from

Conversation

PVince81
Copy link
Contributor

Debugging for #23792

Incomplete fix.

Vincent Petry added 2 commits December 7, 2016 12:43
404 errors were not properly cached due to catching the wrong
exception. Now catching ClientHttpException and checking the error
code. In case of 404, adjust the stat cache accordingly.
@PVince81 PVince81 self-assigned this Dec 12, 2016
@mention-bot
Copy link

@PVince81, thanks for your PR! By analyzing the history of the files in this pull request, we identified @DeepDiver1975, @butonic and @mmattel to be potential reviewers.

Only trigger the discoverymanager in the init method. If the storage
was already marked unavailable, that check will not need to be done
anyway.
@PVince81
Copy link
Contributor Author

PVince81 commented Nov 8, 2017

I already fixed this for stable10 by making the connection lazy init, see #29314

@PVince81 PVince81 closed this Nov 8, 2017
@PVince81 PVince81 deleted the stable9.1-fed-share-lag-test branch November 8, 2017 19:24
@lock
Copy link

lock bot commented Aug 2, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 2, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants