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

GeoFence cache seems to be refreshed every time a layer is uploaded #4125

Closed
capooti opened this issue Dec 14, 2018 · 5 comments
Closed

GeoFence cache seems to be refreshed every time a layer is uploaded #4125

capooti opened this issue Dec 14, 2018 · 5 comments
Assignees
Labels
major A high priority issue which might affect a lot of people or large parts of the codebase

Comments

@capooti
Copy link
Member

capooti commented Dec 14, 2018

GeoFence cache seems to be refreshed every time a layer is uploaded.
This slows down the upload of a layer in our case, with thousands of layers. If I do import the layer with GS importer, logged as the GeoServer admin, it takes just a few seconds.
If I upload it with GeoNode it takes up to 3 minutes.
Is there anything which can be done to mitigate this?

@capooti capooti added the major A high priority issue which might affect a lot of people or large parts of the codebase label Dec 14, 2018
@afabiani afabiani self-assigned this Jan 23, 2019
@afabiani
Copy link
Member

afabiani commented Apr 1, 2019

The PR #4326 should fix the issue.

@capooti
Copy link
Member Author

capooti commented Apr 3, 2019

@afabiani it seems now faster (a layer is uploaded in one minute). But still slow when compared to previous GeoNode version. One thing I have noticed: the geoserver configuration during a layer upload seems being reloaded: is it possible? That would explain the slowness at this point

@afabiani
Copy link
Member

afabiani commented Apr 3, 2019

@capooti nope as far as I can say. There's no command issuing a GeoServer configuration realod.
I kindly suggest to always use the 'geoserver.importer' upload method though, it is more resilient and efficient.

About the slowness, make sure you have enough UWSGI processes and connections available. Remember that now GeoServer asks GeoNode to validate the access tokens. If all the uwsgi processes are busy, it will have to wait the "harakiri" to free new ones.

@afabiani
Copy link
Member

afabiani commented Apr 3, 2019

@capooti you were right. I have found an unattended catalog.reload() while uploading a layer.
By removing that instruction the upload time has been significantly reduced.

@capooti
Copy link
Member Author

capooti commented Apr 4, 2019

yes, @afabiani , it is much much faster now, thanks for fixing that!

@capooti capooti closed this as completed Apr 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
major A high priority issue which might affect a lot of people or large parts of the codebase
Projects
None yet
Development

No branches or pull requests

2 participants