Forum Discussion
Scale-out deployment - weird behavior on one server
Hi anqapl91 ,
Both servers are in version Jan 2021. Before them I have loadbalance URL that is distributing users between servers.
It looks like you are upgrading from a lower version to Jan 2021 (Version: 15.0.1105.230), right?
In addition, have you try to updated the load balancer synchronously?
Best Regards,
Icey
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Hi Icey , thanks for a reply.
I am on Jan 2021 from couple months right now.
By this sentence I ment that my users are using LB link that distributes traffic between nodes. 🙂
Upon further checking I was able to find in the logs that modelsAndExploration method is failing because of the fact that SQL query to ReportServerDB is timing out, Report Server is throwing an exception and unable to build a model.
Now I am kinda puzzled as I cannot check log on DB side (restriced access) and DBA told me this is typically caused by the fact that connection is not using Multi Subnet Failover. I am pretty sure it must be using, but is there documentation available that is describing this connection details?
anqapl91 wrote:
Now I am kinda puzzled as I cannot check log on DB side (restriced access) and DBA told me this is typically caused by the fact that connection is not using Multi Subnet Failover. I am pretty sure it must be using, but is there documentation available that is describing this connection details?
Unfortunately PBIRS does not support multi subnet failover (see https://docs.microsoft.com/en-us/sql/database-engine/availability-groups/windows/reporting-services-with-always-on-availability-groups-sql-server?view=sql-server-ver15#bkmk_reportserverdatabases ) but if this was the issue I would expect that both nodes would be failing. This does not really explain why only one node is not working unless you have the two Report Server nodes connected to different database instances in your AG. You could open up the Report Server Configuration Manager on both nodes to double check that they the database connections are configured to use the same database server instance.
Ah thanks d_gosbell , I was looking everywhere to find this info! 🙂
Both Report Servers are connected using same configuration - through listener for Availability Group - may it be that this second one is connected to a readonly replica?
One more hint - simply removing the report and adding it back in different directory does not help. I am currently observing this issue with two reports, out of over 100. One of them could be really compressed, but is having only Excel as a source and is a size of around 200MB. I am pretty confident developer knows how to model reports, I trust him when it comes to report design. 😃
