Puntos a tener en cuenta con la Cache Distribuida (Distributed Cache) de SharePoint 2013

  • Article

Hola

Nos gustaría recalcar algunos puntos sobre la cache distribuida de SharePoint 2013:

  • NUNCA administres la cache distribuida desde la administración del APPFABRIC del propio cache host. Si haceis eso tendreis que reconstruir el servidor (o incluso la granja) ya que se este pasa a un estado inestable e impredecible

The Distributed Cache service can end up in a nonfunctioning or unrecoverable state if you do not follow the procedures that are listed in this article. In extreme scenarios, you might have to rebuild the server farm. The Distributed Cache depends on Windows Server AppFabric as a prerequisite. Do not administer the AppFabric Caching Service from the Services window in Administrative Tools in Control Panel. Do not use the applications in the folder named AppFabric for Windows Server on the Start menu.

https://technet.microsoft.com/en-us/library/jj219613.aspx

  • La máxima capacidad de memoría reservada para la Distributed Cache por cada cache host es de 16 GB en entornos con más de 16 GB de memoria disponible. Además entornos con más de 16 GB de memoria reservada podrán experimentar retardos inesperadados de 10 segundos

On a server that has more than 16 GB of total physical memory, allocate a maximum of 16 GB of memory to the Distributed Cache service. If you allocate more than 16 GB of memory to the Distributed Cache service, the server might unexpectedly stop responding for more than 10 seconds.  

https://technet.microsoft.com/library/jj219572%28office.15%29.aspx

  • No se soporta memoria dinamica en entornos de SharePoint ni entornos de APP Fabric.

The Distributed Cache service can run on either a physical or virtual server. When using virtualization, do not use Dynamic Memory to manage shared memory resources among other virtual machines and the Distributed Cache servers. The memory allocation for virtualized Distributed Cache servers must be fixed.  

https://technet.microsoft.com/en-us/library/jj219572.aspx

  • El producto al configurarse después de la instalación reserva el 10 % de la memoria RAM que tenga el servidor. Vosotros podeis configurar la cantidad que querais hasta un maximo de 16 GB como expuesto en el siguiente punto.

 

  •  Se recomienda reservar 2 GB para otros servicios. Para calcularla podeis seguir el siguiente ejemplo

When your server farm has a dedicated Distributed Cache server. Use the following method to calculate how much memory can be assigned to the Distributed Cache service: 

  1. Determine the total physical memory on the server. For this example, we will use 16 GB as the total physical memory available on the server.

  2. Reserve 2 GB of memory for other processes and services that are running on the cache host. For example, 16 GB – 2 GB = 14 GB. This remaining memory is allocated to the Distributed Cache service.

  3. Take half of the remaining memory, and convert it to MB. For example, 14 GB/2 = 7 GB or 7000 MB. This is the cache size of the Distributed Cache service

  4. Use the following procedure to update the memory allocation accordingly.

                                     https://technet.microsoft.com/en-us/library/jj219613.aspx

  • No se soportan desarrollos personalizados (API de APPFABRIC) contra el Distrubuted cache de SharePoint 2013. Para ello tendras que montar un cluster separado de APPFABRIC con su propia cache.

https://blogs.technet.com/b/hablamoss/archive/2013/06/05/soportabilidad-desarrollos-sharepoint-2013-y-appfabric-cache.aspx

  • Los códigos de error de APP Fabric que os pueden surgir durante la ejecución de comandos powershell contra el Distributed Cache de SharePoint son los siguientes:

https://msdn.microsoft.com/es-es/library/ff921008(v=azure.10).aspx

  • Actualizar APP Fabric al último CU. Acutalmetne el CU4

                  https://support.microsoft.com/kb/2800726

Muchas Gracias.

Saludos.

Héctor Calvarro Martín. SharePoint Dev/Core. Microsoft Support Escalation Engineer for EMEA