Hello folks, By investigating the stuff, I assume the error is caused by http range request rejection from the side of MinIO. As documentation of COG says ( https://docs.geoserver.org/latest/en/user/community/cog/cog.html), that the plugin is based on these range requests, I found an github issue for minio (https://github.com/minio/minio/issues/5285) which states that multiple http ranges are not supported. However this did not discourage me from trying and I came up with an idea of increasing the it.geosolutions.cog.default.header.length system property. From COG plugin doc:
*By default, when accessing a COG, an initial chunk of 16 KB is read in attempt to parse the header so that the reader will have the offset and length of the available tiles. When dealing with files hosting many tiles, it is possible that the whole header won’t fit in the initial chunk. In this case additional reads (chunks of the same size) will be progressively made to complete loading the header. A it.geosolutions.cog.default.header.length system property can be configured to set the length (in bytes) of the reading chunk. Tuning this so that the header is read with few extra requests can help improve performance. A value too large can cause memory consumption issues and will reduce efficiency, as un-necessary data will be read.* The only thing is that I don't know which is the easiest way to change the system property, since I'm running geoserver in docker container. What do you recommend? Have a nice rest of the day, Marek so 15. 4. 2023 o 16:00 Marek Kadlečík <marekkadleci...@gmail.com> napísal(a): > Hello folks, > I'm playing with the COG plugin and bumping into an error Unable to read > header for <url> (see picture). What does this mean? I translated tif file > beforehand using gdal_translate nejakeId_B02.tif > nejakeId_B02_translated.tif -of COG -co COMPRESS=LZW > As for S3 store I'm using local instance of minio object storage. I found > this piece of email communication > https://sourceforge.net/p/geoserver/mailman/message/37227114/, where the > problem seems to be the minio refusing the range requests. I hope the > convention <adress>:<port>/<bucket_name>/<object_name> still applies also > in minio. > > Do you guys know where the problem could be? Would help me a lot. > > Best regards, > > Marek > > >
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
