A problem with metadata:FilesystemMetadataProvider
Cantor, Scott
cantor.2 at osu.edu
Mon Aug 11 11:00:49 EDT 2014
On 8/11/14, 10:52 AM, "Marco Malavolti" <marco.malavolti at garr.it> wrote:
>Yes, I have set these so low in order to reproduce the issue more
>quickly, but I have the same problem with the default configuration
>values:
>- minRefreshDelay="PT5M"
>- maxRefreshDelay="PT4H"
Then your file has a last-modified value that's older than every time it
runs a check. Trust me, it works, so the only way it's not working is if
you're essentially forcibly causing the race condition every time. Your
tests won't mean anything unless you keep the timestamp on the file new
enough to trigger a load.
What you want is for the file time to be essentially the exact time you
update the file, not the actual time the file was last changed at the
source.
Basically, either change your file update process, or switch to the HTTP
versions.
-- Scott
More information about the users
mailing list