Log entries for admin copy cache events

 Admin copy cache event triggered by definition change

A definition change received for copy cache marks the copy cache event and includes the following parameters:

• tid - Thread ID
• user - User who triggers the event

Here is an example of the log entry:

CopyCache: CreateNewCache indicates that a new cache must be created, it marks the cache event, and includes the thread ID ( tid ).

Here is an example of the log entry:

A definition change might not trigger creation of a new cache if it is received during a delay recache period (see Best-practices-for-preventing-cache-memory-issues). In this case, the existing admin cache is used. This is shown in the following log example:

CopyCache Begin marks the beginning of the copy cache event, if a new cache is being created. This event includes the following parameters:

• cacheID - The cache ID of the current cache
• rpcCallProc - Remote procedure call value
• tid - Thread ID
• rpcid - The unique ID of the remote procedure call
• numCaches - The current number of caches in the process
• maxNumCaches - The maximum number of caches allowed for the process, based on the configuration

Here is an example of the log entry:

CopyCache End marks the end of the copy cache event, and includes the following parameters:

• new cacheId - The ID of the new cache
• old cacheId - The ID of the current cache
• threadCount - The number of threads holding the current cache
• tids - The IDs of the threads holding the current cache

Here is an example of the log entry:

cacheChange Completed indicates the end of the cache change event. Here is an example of the log entry:

Admin Cache Promoted occurs after the delayRecacheTime has elapsed, and if no more definition changes are queued. This entry logs the completion of the copy cache event, and includes the following parameters:

• cacheID - The new cache ID
• cacheIdToFree - The ID of the current cache that is to be released

Here is an example of the log entry:

The copy cache event is followed by a FreeServerCache event, as seen in the following example:

For more information about FreeServerCache, see Log-entries-for-free-server-cache-events.

 Admin copy cache event triggered by Group/User change

When a group or user change occurs, a copy cache event is triggered. This event is marked by the Group/User Change Received entry, and includes the following parameters:

• tid - The thread ID
• user - The user who triggers the event
• userOrGroup - Indicates a user or group change
• groupRecacheIsPending - Indicates that the event is pending based on a previous change.
• delayRecacheTime - The amount of time this copy cache event will be delayed, based on your configuration
• Add request to Timer Queue - Indicates the amount of time the copy cache event will be delayed based on the configured delayRecacheTime.
• Add request to Admin thread - Marks the completed delayRecacheTime .
• AR_INTERNAL_REQ_GROUP_CHANGED Started - Indicates the start of the copy cache event.

Here is an example of the log entry:

Here is an example of the log entry for the actual copy cache:

After a copy cache event, the group permissions are reloaded from the database. This is indicated with the AR_INTERNAL_REQ_GROUP_CHANGED Completed log entry as shown in the following example:

Admin Cache Promoted occurs after the delayRecacheTime has elapsed, and if no more changes are queued. This entry logs the completion of the copy cache event as shown in the following example:

The copy cache event is followed by a FreeServerCache event, as shown in the following example:

For more information about FreeServerCache, see Log-entries-for-free-server-cache-events.