KVM Cache refresh in Apigee x

[kmohit520]

Hi All

As per the below documentation, KVM refreshes it's cache based on <ExpiryTimeInSecs> parameter in GET operation of KVM.

https://cloud.google.com/apigee/docs/api-platform/reference/policies/key-value-map-operations-policy

• So if there are 10 proxies having KVM-Get operation with different <ExpiryTimeInSecs> configured, which one will be applied for KVM cache refresh?
• Also, does it loads whole data from KVM into the cache from Cassandra OR it loads only the particular key/value used in policy?

[ganadurai · Accepted solution]

• So if there are 10 proxies having KVM-Get operation with different <ExpiryTimeInSecs> configured, which one will be applied for KVM cache refresh?
  You should be using sharedflow in this scenario so all proxies use the same KVM policy with a single ExpiryTimeInSecs. In case you have dont have a sharedflow, the chache clock ticks from the first GET operation. Check out the sample scenario explained in the doc. under the section "Example - Caching a KVM"
  
  
• Also, does it loads whole data from KVM into the cache from Cassandra OR it loads only the particular key/value used in policy?
  Its the key/value that queried via KVM GET.