The following attributes are supported only on for the dynamic metadata providers "dynamic" (on-demand) MetadataProvider types (MDQ, Dynamic, LocalDynamic):
| Name | Type | Default | Description |
|---|
cleanupInterval |
Integer| time in seconds | 1800 (30 mins) | Time in seconds between execution of background thread to scan for expired cached metadata and remove it from memory. |
Set You can set this to 0 to disable any cleanup, but this will potentially cause memory usage to grow. |
cleanupTimeout |
Integer| time in seconds | 1800 (30 mins) | Extra time to leave |
"stale" | recently-unused entries in the cache before the background cleanup process will remove them |
.Integer| time in seconds | 28800 (8 hours) | Upper bound on time before attempt to reload metadata for an entity |
will be re-acquiredInteger| time in seconds | 600 (10 mins) | Lower bound on time before attempt to reload metadata for an entity |
will be re-acquired.Decimal| decimal | 0.75 | Factor applied to the metadata's own validity or caching period to determine the reload interval to use. Once applied, the result is bounded by the minCacheDuration and maxCacheDuration settings to determine the time of the next attempt. If reload attempts fail, the existing metadata (if any) will be reused until it actually expires |
negativeCache |
Boolean| boolean | see description | Controls whether lookup failures |
to lookup are cached (for the minCacheDuration). This can avoid repeatedly |
hitting accessing a server which is |
known not to cache datafailing or simply has no metadata. Defaults to "true" for remote dynamic metadata providers (MDQ, Dynamic) and "false" for |
the