Yes, confirmed, it's happening while the WFS 1.1&/2.0 GetFeature tries to compute the total features matched. The store lacks an efficient path to perform such a count, and resorts to a "load everything and filter in memory".
So far the store has only been used (in production) for WMS purposes and this code needs to be developed to efficiently support WFS usage (or just use WFS 1.0, does not seem to happen in that case, at least for GML output). I'd recommend to open a jira ticket, and then, if you are in any urgent need to get a fix, look at this guide: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-fixes,-improvements-and-new-features-in-GeoServer (consider the talking part done, it's the resourcing part that is missing) Regards, Andrea Aime == GeoServer Professional Services from the experts! Visit http://bit.ly/gs-services-us for more information. == Ing. Andrea Aime @geowolf Technical Lead GeoSolutions Group phone: +39 0584 962313 fax: +39 0584 1660272 mob: +39 339 8844549 https://www.geosolutionsgroup.com/ http://twitter.com/geosolutions_it ------------------------------------------------------- Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia. This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail On Tue, Mar 19, 2024 at 9:28 PM Richard Matsunaga via Geoserver-users < geoserver-users@lists.sourceforge.net> wrote: > Hi Andrea, > > > > The SLD= was a mistake and has been removed. Has no effect anyway it seems. > > > > I checked the bounding boxes produced for each row and they seems fine. I > then built a query with Postgis to filter by a bounding box and it returned > a subset of results. > > > > The logs show this query and, unless it is incomplete, it does not seem to > be filtering by the bounding box at all. > > SELECT "ogc_fid",encode(ST_AsEWKB("wkb_geometry"), 'base64') as > "wkb_geometry","params" FROM "vector_products"."raw_points_index"; > > Richard > > > > *From:* Andrea Aime <andrea.a...@geosolutionsgroup.com> > *Sent:* Tuesday, March 19, 2024 5:23 AM > *To:* Richard Matsunaga <richard.matsun...@troo.com> > *Cc:* geoserver-users@lists.sourceforge.net > *Subject:* Re: [Geoserver-users] WFS query of a Vector Mosaic datastore > > > > You don't often get email from andrea.a...@geosolutionsgroup.com. Learn > why this is important <https://aka.ms/LearnAboutSenderIdentification> > > Hi Richard, > > the mosaic should query and open only the files whose geometry, in the > mosaic index, intersects the bbox you provided. > > So first, check the mosaic index, which entries are actually matching the > provided bbox? > > > > The "&sld" bit does not make sense in a GetFeature, makes me wonder if > you're passing it by mistake, or if you have some > > customization/plugin that makes use of it? > > > Regards, > > Andrea Aime > > > > == > GeoServer Professional Services from the experts! > > Visit http://bit.ly/gs-services-us for more information. > == > > Ing. Andrea Aime > @geowolf > Technical Lead > > > GeoSolutions Group > phone: +39 0584 962313 > > fax: +39 0584 1660272 > > mob: +39 339 8844549 > > > > https://www.geosolutionsgroup.com/ > > http://twitter.com/geosolutions_it > > ------------------------------------------------------- > > > Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE > 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si > precisa che ogni circostanza inerente alla presente email (il suo > contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è > riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il > messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra > operazione è illecita. Le sarei comunque grato se potesse darmene notizia. > > This email is intended only for the person or entity to which it is > addressed and may contain information that is privileged, confidential or > otherwise protected from disclosure. We remind that - as provided by > European Regulation 2016/679 “GDPR” - copying, dissemination or use of this > e-mail or the information herein by anyone other than the intended > recipient is prohibited. If you have received this email by mistake, please > notify us immediately by telephone or e-mail > > > > > > On Fri, Mar 15, 2024 at 10:19 PM Richard Matsunaga via Geoserver-users < > geoserver-users@lists.sourceforge.net> wrote: > > Hello, > > > > We are using the Vector Mosaic datastore ( > https://docs.geoserver.org/main/en/user/community/vector-mosaic/index.html). > It seems to functioning well for our needs except for one case. > > > > With a WFS GetFeature request, the response time is so slow our load > balancer times out before the response comes back grom GeoServer. The > timeout is 1 min, a typical WFS GetFeature request takes about 2 mins > according to the GeoServer logs. > > > > Our mosaic index is stored in PostgreSQL and the mosaic flat files are > FlatGeoBuf. > > > > From the GeoServer logs, it appears that the entire index is being queried > instead of being filtered by the input bounding box to the GetFeature. We > have over 1000 rows in the index. I am guessing each of these files are > then being queried against the bounding box, but I’m not sure. > > > > It starts with this query: > > > > SELECT "ogc_fid",encode(ST_AsEWKB("wkb_geometry"), 'base64') as > "wkb_geometry","params" FROM "vector_products"."raw_points_index"; > > > > Then we get many entries like: > > > > [geotools.vectormosaic] - Found and set datastore for granule null with > params {url=file:/ > /GeoserverData/farmtrx/raw_points/dALzgubWabg8nVZlObJZU_raw_points_32814/dALzgubWabg8nVZlObJZU_raw_points_32814.fgb} > > > > Eventually it seems to succeed, but long after the gateway timed out: > > > > "GET > /geoserver/wfs?service=WFS&version=2.0.0&request=GetFeature&outputFormat=application/json&bbox=-8428045.938524414,5672717.233576572,-8427400.045285502,5673091.775131803,EPSG:3857&typeName=raw_points&SLD=file:/// > /styles/abXuSt4KMlbFn8SG84bHX/abXuSt4KMlbFn8SG84bHX_33272_raw_points_hct.sld&count=100&propertyName=yldt_ha" > took 119988ms > > > > Previously we stored all the vector data in PostgreSQL and this GetFeature > query returned nearly instantaneously. Am I correct that it seems the > original query would be better to be filtered by the bounding box, thus > returning one or a few rows? > > > > Thanks, > > Richard > > _______________________________________________ > 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 > > _______________________________________________ > 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 >
_______________________________________________ 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
