I am having a custom report modifying the request fields of projects. The modification is done by adding a row to a request table component (KCRT_TABLE_ENTRIES).
The problem is, I am having problems flushing the cache afterwards, meaning the modification is not visible. It is a cluster, and it seems the main node is having its caches cleared as changes are visible immediately, but the other nodes are not having the changes visible immediately.
I am using "kRunCacheManager A" for flushing all caches.
I'm not sure that kRunCacheManager will automatically detect a cluster and flush them all.
However, if you update the LAST_UPDATE_DATE & LAST_UPDATED_BY in kcrt_requests and kcrt_request_details tables too then the servers should all know their cached data for this request is outdated without having to do a manual flush...
indeed the clustered environment could be an issue. Try to disable the table entry cache in all servers of clustered environment in /conf/tune.conf edit the following line and set cache size to zero com.kintana.core.server.TABLE_ENTRY_CACHE_SIZE = 0
Alternatively, is there a command to flush the table_entry_cache? I've faced this problem earlier and flushing the cache with the available commands just flushes the request details cache and not the table component's. Thanks!