Processing OLAP Cube causes OLAP and SQL to shut down

Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to th
e
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would fai
l
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before, bu
t
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.Yes! Resource contention. If you are trying to run 6 instances of SQL
Server and at least 1 Analysis Services server on only a two node cluster,
you most assuradely have resource contention and it is called MEMORY, which,
too, is most assuradely used during the building of the cube.
How much memory are you running on those two nodes? What is the MAX SERVER
MEMORY configuration set to on each of the instances? What is the setting
for the source of the OLAP cube? Anything short of about 512 MB to 1 GB for
each instances, plus about 1 GB for the Analysis Services, is under capacity
for any real use production system.
Do you have 6 to 12 or so GB on EACH node?
Sincerely,
Anthony Thomas
"TX_KniveS" <TX_KniveS@.discussions.microsoft.com> wrote in message
news:9C541BA2-E1B4-46C8-8F1D-3D1D145A622C@.microsoft.com...
Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to
the
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would
fail
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before,
but
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.

Processing OLAP Cube causes OLAP and SQL to shut down

Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to the
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would fail
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before, but
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.Yes! Resource contention. If you are trying to run 6 instances of SQL
Server and at least 1 Analysis Services server on only a two node cluster,
you most assuradely have resource contention and it is called MEMORY, which,
too, is most assuradely used during the building of the cube.
How much memory are you running on those two nodes? What is the MAX SERVER
MEMORY configuration set to on each of the instances? What is the setting
for the source of the OLAP cube? Anything short of about 512 MB to 1 GB for
each instances, plus about 1 GB for the Analysis Services, is under capacity
for any real use production system.
Do you have 6 to 12 or so GB on EACH node?
Sincerely,
Anthony Thomas
"TX_KniveS" <TX_KniveS@.discussions.microsoft.com> wrote in message
news:9C541BA2-E1B4-46C8-8F1D-3D1D145A622C@.microsoft.com...
Here's a situation I ran in recently, and I'm trying to discover root cause.
I should mention this was occuring on a active/active two-node cluster w/ 6
instances of SQL running on it. The OLAP service in question was tied to
the
SQL Server service as part of the same cluster group.
I had a cube in OLAP I was attempting to process, but each time I tried the
OLAP service and the SQL Server Service that OLAP was using as a data source
would shut down and fail over to another cluster node. This would
continually happen each time we would try to process the cube - it would
fail
over back and forth to the two nodes on the cluster.
Finally when we manually took the cluster group down and brought it back up,
everything stabilized. Not sure why this smoothed things out as the SQL
Server instance and the OLAP service had been on the correct node before,
but
now that we had moved the instance manually, everything was fine.
My only guess as to root cause was contention for resources. Does anybody
else have any ideas? Again, the problem I'm trying to understand is why
processing a cube will cause a SQL Server and OLAP instance to shut down.
Thanks in advance.