EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB15245: In a clustered environment with centralized caching, nodes are not sharing caches but are creating their own caches in MicroStrategy Intelligence Server Universal


Community Admin

• Strategy


When executing a report on MicroStrategy Desktop on Node1 and creating a cache and then connecting to Node2, it does not use the current cache but re-executes the report, creates a new cache in Node2's cache folder, and deletes the original existing cache.

SYMPTOM:
When executing a report on Strategy Desktop on Node1 and creating a cache and then connecting to Node2, it does not use the current cache but re-executes the report, creates a new cache in Node2's cache folder, and deletes the original existing cache.
Administrators can observe this behavior in detail if Report Server -> Cache Tracing is turned on. The following cache trace message shows the current cache being saved from the Node1 Strategy Intelligence Server Universal 8.x:
 


2006-11-10 10:58:58.440-05:00 [HOST:Node1][PID:3550][THR:3313719664][Report Server][Cache Trace] CDSSCachedReport::hSaveToFile starts writing into file /SharedCaches/ServerNode1_P41E2D02631DA70C08A9600802955EAEE/Cache449ED84131DB70D4A9C80080BFEFA4F9.che

2006-11-10 10:58:58.520-05:00 [HOST:Node1][PID:3550][THR:3313719664][Report Server][Cache Trace] CDSSCachedReport::hSaveToFile completes writing into file /SharedCaches/Node1_P41E2D02631DA70C08A9600802955EAEE/Cache449ED84131DB70D4A9C80080BFEFA4F9.che

 
Below, Node2 is now looking for the cache that was created above in Node1's cache folder. Note that it is not looking in the correct SharedCaches location:
 

2006-11-10 11:03:47.110-05:00 [HOST:Node2][PID:3550][THR:1304516976][Report Server][Cache Trace] Trying to read remote cache info with ID 449ED84131DB70D4A9C80080BFEFA4F9, cache file path //Node1/ClusterCaches/Node1_P41E2D02631DA70C08A9600802955EAEE/Cache449ED84131DB70D4A9C80080BFEFA4F9_Info.che.
2006-11-10 11:03:47.140-05:00 [HOST:Node2][PID:3550][THR:1304516976][Report Server][Cache Trace] Cache Info file for remote cache with ID 449ED84131DB70D4A9C80080BFEFA4F9 has file status of -1, file not found.
2006-11-10 11:03:47.140-05:00 [HOST:Node2][PID:3550][THR:1304516976][Report Server][Cache Trace] Get Cached RI try to load cache result from cluster which return error code 828

 
CAUSE:
The Administrator has defined the Shared Location for the Caches for this Project as /SharedCaches as shown below:
 

ka04W000000OfVgQAK_0EM440000002BXq.jpeg

 
This path specification is interpreted by the Intelligence Server as a local path, and not as a shared cache location. When trying to access the same cache from the second node (Node 2), the Intelligence Server on that node will attempt to look for a shared location called "//Node1/ClusterCaches" and will be unable to locate the cache file. This logic applies to the shared Inbox folders as well.
 
ACTION:
For Centralized Caching, Administrators must define the Cache File Directory with \\SharedCaches. If not, Strategy Intelligence Server 8.x will recognize the path of /SharedCaches as a relative path when looking for Shared Caches. One note of interest is that even with the Cache file directory set as /SharedCaches, and if the centralized file storage is mounted on this folder, the files will be correctly created by the nodes in the desired location. For more details on setting up a clustered Intelligence Server Universal platform, please see the Technical Note:
 
TN14607 - How to set up clustered Cache and Inbox sharing for the Strategy Intelligence Server Universal
 


Comment

0 comments

Details

Knowledge Article

Published:

April 3, 2017

Last Updated:

April 3, 2017