-
Notifications
You must be signed in to change notification settings - Fork 34
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
Circular dependency between FragmentRender and RendererFactory #7890
Labels
Comments
|
It took me longer than I hoped. So, there is a "quickfix" which is still not the best and not so quick :( |
rymsha
added a commit
that referenced
this issue
Feb 20, 2020
vbradnitski
added a commit
that referenced
this issue
Feb 25, 2020
Circular dependency between FragmentRender and RendererFactory #7890
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is not a hypothetical issue. OSGi Circular Reference exception happens every now and then during startup.
It is likely to happen when Elasticsearch gets active almost immediately during application startup. So it happens in clustered environment when other ES nodes are fully ready and cluster check succeeds immediately.
By looking at the code I can say that RendererFactory is a needless registry on top of OSGi Component registry and could be refactored in a way that it does not hold references to all Renderers.
The text was updated successfully, but these errors were encountered: