Export (0) Print
Expand All

Manage Feed Cache and Last Modified Time Cache repopulation in SharePoint Server 2013

SharePoint 2013

Updated: February 19, 2013

Summary: Learn how to manage repopulation of the Feed Cache and Last Modified Time Cache in SharePoint Server 2013.

Applies to:  SharePoint Server 2013 

SharePoint Server 2013 feeds require the Feed Cache and Last Modified Time Cache. The Feed Cache maintains recent conversations and activities of entities. The Last Modified Time Cache maintains the last modified time for all items in the Feed Cache. The Distributed Cache service manages both the Feed Cache and the Last Modified Time Cache.

System events, such as a server shutting down unexpectedly physical events such as electrical power spikes can affect the Distributed Cache service. Additionally, an administrator who performs maintenance and operational tasks can take an application server that runs the Distributed Cache service offline. This results in the resetting and emptying of the Feed Cache and the Last Modified Time Cache. In this situation, repopulation of the recent conversations and activities of entities occurs. Repopulation occurs in two stages:

  1. Load last modified time information for recent conversations and activities.

  2. Load recent conversations and activities.

note Note:

In the case of planned maintenance and operations, an administrator can preserve cache data by using the graceful shutdown procedure. For more information, see Perform a graceful shutdown of the Distributed Cache service in Manage the Distributed Cache service in SharePoint Server 2013.

To manage the repopulation process, SharePoint Server 2013 includes the Feed Cache Repopulation Job timer job. When the Feed Cache Repopulation Job timer job runs, it first checks whether the Feed Cache and Last Modified Time Cache are empty. If they are empty, it starts repopulating the last modified time information for recent conversations and activities in the Last Modified Time Cache. After the timer job finishes the Last Modified Time Cache repopulation, the Feed Cache is populated with recent conversations and activities the next time any user accesses a feed in SharePoint Server 2013.

In this article:

Feed Cache settings on the User Profile Service application

An administrator might configure properties on the User Profile Service application that changes the default behavior of the Feed Cache in SharePoint Server 2013. For example, the maximum number of posts per entity that can be stored in the Feed Cache is set to a default value of 500. When this maximum value is reached, the Feed Cache will delete 200 posts to allow the entity to continue posting. Updating these properties might take 5 to 10 minutes to take effect because this is the time it takes to propagate. Other content following limits can take 5 to 10 minutes if you have more than one server.

The following table lists parameters to set for the Feed Cache on a User Profile Service application.

Table: Feed Cache parameters for a User Profile Service application

Feed Cache settings on the User Profile Service application Description Default value

FeedCacheTTLHours

The default Time To Live of entries in feed cache in hours. For example, setting this property to 168 (hours) will store entries in the Feed Cache for 7 days.

168

FeedCacheLastModifiedTimeTtlDeltaHours

Additional time added to keep FeedCacheTTLHours for LMT entries. LMT items are kept for 14 days. 7 days for FeedCacheTTLHours plus 7 days for FeedCacheLastModifiedTimeTtlDeltaHours.

168

FeedCacheObjectCountLimit

The maximum number of posts for a given entity that can exist in feed cache.

500

FeedCacheRoomForGrowth

The amount of posts to delete when the number of posts for a given entity reaches FeedCacheObjectCountLimit.

200

Use the following cmdlet with these parameters to make changes to the Feed Cache settings on the User Profile Service application:

For example, to set the FeedCacheTTLHours parameter, run the following cmdlet:

$upa = Get-SPServiceApplication | where {$_.TypeName -Like "User Profile Service Application"}
$upa.FeedCacheTTLHours = 96
$upa.Update()

Where 96 represents the number of hours entities will stay in the Feed Cache.

The following cmdlets are available to force repopulation of the Feed Cache and the Last Modified Time Cache:

Repopulate the Last Modified Time Cache by using timer jobs in Central Administration

The User Profile Service Application - Feed Cache Repopulation Job repopulates the Last Modified Time Cache if the Distributed Cache service resets and becomes empty. Also, after you configure My Sites, users will not see posts appearing in their consolidated newsfeed if the User Profile Service Application - Feed Cache Repopulation Job timer job is not configured to run. By default, the User Profile Service Application - Feed Cache Repopulation Job timer job is configured to run every 5 minutes.

Use this procedure to configure the User Profile Service Application - Feed Cache Repopulation Job timer job to monitor the Feed Cache and Last Modified Time Cache for repopulation.

Important Important:

Do not change the default settings of this timer job if you plan to use social features in SharePoint Server 2013. Do not disable this timer job. If this timer job is disabled and a repopulation is required, it will re-enable itself and run.

To configure the User Profile Service Application - Feed Cache Repopulation Job

  1. Verify that you have the following administrative credentials:

    • To configure timer jobs, you must be a member of the Farm Administrators group on the computer running the SharePoint Central Administration website.

  2. In Central Administration, on the Monitoring page, click Review job definitions.

  3. On the Job Definitions page, in the View list, select All.

  4. Use the arrows at the bottom of the page to locate the feed cache repopulation job for the User Profile service application on your server farm. The job name is in the format User_Profile_service_name - Feed Cache Repopulation Job, where User_Profile_service_name is the name that you specified for the User Profile service application.

  5. On the Edit Timer Job page, in the Recurring Schedule section, select the interval that you want the job to run. Available intervals are Minutes, Hourly, Daily, Weekly, and Monthly. Selecting a shorter interval, such as Minutes or Hourly, ensures that checks for an empty cache is performed more frequently. Selecting a longer interval, such as Daily, Weekly, or Monthly, reduces the number of times the job runs. However, it also means that performing cache repopulation checks are done fewer times. We recommend that this timer job runs on shorter intervals.

  6. Click Enable.

  7. Optionally, click Run Now to run the job immediately without waiting for the next scheduled interval.

Repopulate the Feed Cache and Last Modified Time Cache by using Windows PowerShell cmdlets

You can use Windows PowerShell cmdlets to perform the repopulation of the Feed Cache and the Last Modified Time Cache. To perform repopulation, we recommend that you configure the User Profile Service Application - Feed Cache Repopulation Job timer job as described above. This is because the timer job first checks to see whether the cache is empty and then repopulates the cache as necessary, whereas the Windows PowerShell cmdlets force a repopulation of the cache. However, in some instances, using the Windows PowerShell cmdlets is the only way to repopulate the cache. These instances include the following:

  • After attaching a new content database and the cache is not repopulating.

  • After restoring a content database.

The following cmdlets are available to force repopulation of the Feed Cache and the Last Modified Time Cache:

Change History

Date Description

February 19, 2013

Added new section: "Feed Cache settings on the User Profile Service application."

July 16, 2012

Initial publication

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft