Hook into GeoServer refresh API to re-load FSDS data store cache

Hook into GeoServer refresh API to re-load FSDS data store cache

• Added File System(GeoMesa) as datastore.
• user comand tool ingest new feature type. ./bin/geomesa-fs ingest -f poi -p /tmp/fsds/ --partition-scheme z2-2bits --encoding orc --force ./poi.geojson3.

3. in create feature type page, the newly ingest feature type will not show in add map layer resource list after select my geomesa datastore.

4. but after restart geoserver it will show up in the resource list.

5. I tried call geoserver reload API, it won’t show up as well.

Original JIRA Issue: https://geomesa.atlassian.net/browse/GEOMESA-3181

Key: GEOMESA-3181
Type: Improvement
Priority: Major
Status: To Do
Resolution: Unresolved
Reporter: 吴常亮
Created: Tue, 1 Mar 2022 22:35:42 -0500
Updated: Wed, 8 Jun 2022 08:52:23 -0400

Comments:

557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Wed, 2 Mar 2022 09:14:02 -0500):

Have you tried waiting 10-15 minutes? By default the filesystem state is cached to avoid repeated reads, which isn’t really an issue with a local filesystem but becomes important with s3. If you want to reduce the cache, you can configure it here: https://www.geomesa.org/documentation/stable/user/filesystem/configuration.html#geomesa-fs-file-cache-duration

Please let me know if that works for you!
Regardless, there may be a way to hook into the ‘reload’ api to force the cache to expire.

5aa78abcd965062a7936cace (Wed, 2 Mar 2022 21:13:33 -0500):

Thanks, it works!
Yes, I missed the config. And it is quite hard for a new user to know it is a geoserver issue or geomesa issue, which both I used for the first time.
I tried to find the soltion in geoserver user manual…

557058:da7f6dfa-f0a1-468b-aec5-2cb61273feb5 (Thu, 3 Mar 2022 09:08:26 -0500):

Great!. I’ll leave the bug open, because there probably is a way we could hook into the ‘refresh’ api to avoid the issue.

Start with the GeoServer refresh API entry point and the GeoMesa filesystem cache configuration referenced in the issue. Reproduce the flow with the geomesa-fs ingest command, then check the create feature type page and resource list. Done means a refresh makes a newly ingested feature type visible without restarting GeoServer.