Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Earn the coveted Fabric Analytics Engineer certification. 100% off your exam for a limited time only!

Reply
kumar09
Frequent Visitor

Power BI Report Server Refresh schedule not syncing the data in a scale out environment

 

Hi Power BI Community -

 

I'm seeing an issue with scheduled refresh in a scale out Power BI Report Server setting.

 

One of my report is developed by using imported mode data source and we have setup a scheduled refresh to keep the data upto date. If the scheduled refresh job runs on serverA then when I access the report and if the request gets served from ServerA I can see the latest data and if some of the widgets in the report gets served by serverB then I still get the old data. I can see from where the requests were served from ExecutionLog3 table. I have seen some post by Daniel_Altevogt  where they were suggesting to redue the "ModelExpirationMinutes" which I dont feel comfortable doing as its going to reduce the performance. This seems to a bug to me. Has any faced the same scenario? 

3 REPLIES 3
Jon-Heide
Employee
Employee

The behavior is expected, due to caching. Server-B will only pick up an updated model after (1) Server-A's refresh has completed and it has committed the model back to the shared report server catalog database and (2) A new session is created on Server-B. 

 

Sessions are per server, per user and a timeout. Sessions are extended by the client browser when in use. So, in this case you can decrease the session timeout. The performance risk would be, if there are other users on that server that open and view reports & leave it idle past the session timeout... then they'll need to take the latency hit to reload the model.

Thank you Jon for the update. So inorder to get the most updated data to the user I need to reduce "SessionTimeout" property from its default value 600s to some where less than 300s (less than 5 mins). I'm also wondering how are "ModelExpirationMinutes" and "ModelCleanupCycleMinutes" have effect on this process.

I usually lower "ModelExpirationMinutes" and "ModelCleanupCycleMinutes"  to 15 mintes from default 60 minutes for scale-out deployment. There is no clear guide line from Microsoft regarding this.

Helpful resources

Announcements
April AMA free

Microsoft Fabric AMA Livestream

Join us Tuesday, April 09, 9:00 – 10:00 AM PST for a live, expert-led Q&A session on all things Microsoft Fabric!

March Fabric Community Update

Fabric Community Update - March 2024

Find out what's new and trending in the Fabric Community.