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

Artefacts on tiles when using apache module #291

Open
FoxAndOps opened this issue Sep 23, 2022 · 8 comments
Open

Artefacts on tiles when using apache module #291

FoxAndOps opened this issue Sep 23, 2022 · 8 comments

Comments

@FoxAndOps
Copy link

We are experiencing some strange artifacts on tiles when using the mapcache apache module, but not when using fcgi.

mapcache_artefacts

Sources are wmts services.
I have been testing in docker containers using the exact same versions of dependencies (including Gdal 3.5.1 - as it is used for wmts sources) and Mapcache (1.12.1).
Deleting the affected tiles and redownloading them or waiting for tile expiration fixes this issue.

We have been running mapcache in production through fcgi for quite some time now and I am 100% sure artifacts do not happen.
We switched to fcgi because of this issue.

Any idea what could be causing these artifacts, and why it only happens with apache module ?

@sdlime
Copy link
Member

sdlime commented Sep 23, 2022

This might be a good question for the mailing lists to start - more eyes. I've been running MapCache using the Apache module for years and have never seen anything like it.

@marisn
Copy link
Contributor

marisn commented Feb 1, 2023

What kind of backend are you using? Do you pre-seed your tiles or are they cached on-the-fly?

@FoxAndOps
Copy link
Author

Tiles are stored on disk, and cached on-the-fly.

@sdlime
Copy link
Member

sdlime commented Feb 1, 2023

Wonder if the MapCache 1.14.0 makes a difference?

@FoxAndOps
Copy link
Author

FoxAndOps commented Feb 15, 2023

Wonder if the MapCache 1.14.0 makes a difference?

Sadly, it doesn't.
I just updated Mapcache to 1.14.0 & Gdal to 3.6.2 but artefacts still appear when using the mapcache module.

@sdlime
Copy link
Member

sdlime commented Feb 15, 2023

Can you isolate the WMS call that creates the image that mapcache carves into tiles? Would be good to verify the artifacts aren't in the source material.

@marisn
Copy link
Contributor

marisn commented Feb 15, 2023

If you are certain your WMTS source is OK, I would suggest to give LMDB a try. Although it will not shine any light on the root of problem, it is a workaround to try.
When MapCache runs as a module, complexity of debugging increases immensely as bugs might be timing-sensitive due to access patterns of shared resources among threads. I had frequent corruptions with on-fly BDB cache under load and sunk a lot of hours trying to figure out what was causing it without a success. Finally I implemented LMDB cache and for a few months haven't had a single problem. YMMV

@FoxAndOps
Copy link
Author

@marisn : I tried LMDB as you suggested, and so far so good !
A huge thank you to you !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants