Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 123»»»

Qourum disk running low on disk space Expand / Collapse
Author
Message
Posted Wednesday, September 25, 2013 11:41 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Today @ 8:17 AM
Points: 80, Visits: 210
I have a multi instance sql server 2008 cluster running on windows server 2003. On the node that owns the quorum disk I keep getting messages that the quorum disk is running low on disk space. My question is whats cauing the quorum disk to fill up and how can I prevent the quorum disk form getting full

Thanks
Post #1498514
Posted Friday, October 4, 2013 3:56 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 5:45 AM
Points: 127, Visits: 307
Check all the folders exists on Qouram Disk for space. Normally the size of Qouram should not be more then few MB's if there are not much of logs. You can check old logs and clear it in case that is not required. But i doubt, logs will cause space issue.
Post #1501781
Posted Friday, October 4, 2013 4:39 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Today @ 8:17 AM
Points: 80, Visits: 210
Thanks for your reply, however the strange part is when I view the quorum disk through windows explorer, I cannot see what is filling up the disk. I could try increasing the space available to the quorum drive but that's just a fix not a root cause solution. The quorum disk is on a SAN and the cluster nodes are virtualized, so even increasing disk space would need an outage but so far I haven't had any luck finding out what's steadily eating up disk space.



Post #1501785
Posted Saturday, October 5, 2013 3:11 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 1:53 PM
Points: 35,366, Visits: 31,905
I have a similar problem that turns out to be some rather inefficient code that truncates several very large tables and reloads ALL of the data from an AS 400 every bloody night. Folks are in the process of repairing the code for performance and I'm in the process of moving the tables to a dedicated database in the SIMPLE recovery mode and to a separate set of disks not on the SAN.

My recommendation would be to run a server side trace for anything that takes too long or writes too much data. It's something that should be done once in a while even if it's not affecting quorum size.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1501865
Posted Monday, October 7, 2013 5:52 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Today @ 8:17 AM
Points: 80, Visits: 210
Thanks for your reply Jeff, but Im unable to make the corelation between inefficient code and the quorum disk running low on disk space.
Would you be ableto elaborate on the connection between the two ?
Post #1502093
Posted Monday, October 7, 2013 5:58 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:09 PM
Points: 40,204, Visits: 36,605
Jeff Moden (10/5/2013)
I have a similar problem that turns out to be some rather inefficient code that truncates several very large tables and reloads ALL of the data from an AS 400 every bloody night. Folks are in the process of repairing the code for performance and I'm in the process of moving the tables to a dedicated database in the SIMPLE recovery mode and to a separate set of disks not on the SAN.


Why would that affect the cluster's quorum drive?



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1502095
Posted Monday, October 7, 2013 1:00 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Tuesday, May 6, 2014 5:45 AM
Points: 127, Visits: 307
Jeff, I am wondering doing anything in your DB, changing Database recovery model or performance issue on DB has anything to do with Quorum Drive...Quorum Drive is Database for your cluster.. So think from the angle that why your Quorum Drive is filling up fast, have you placed any thing else there or Quorum server log is filling it up.
Post #1502317
Posted Monday, October 7, 2013 3:42 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Today @ 8:17 AM
Points: 80, Visits: 210
@Dhananjay,
From Windows explorer the only directories I see are the MSCS and MSDTC, there is nothing else that I can see that could be steadily eating up the disk space on the quorum drive.
Post #1502395
Posted Monday, October 7, 2013 4:15 PM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: General Forum Members
Last Login: Yesterday @ 1:53 PM
Points: 35,366, Visits: 31,905
GilaMonster (10/7/2013)
Jeff Moden (10/5/2013)
I have a similar problem that turns out to be some rather inefficient code that truncates several very large tables and reloads ALL of the data from an AS 400 every bloody night. Folks are in the process of repairing the code for performance and I'm in the process of moving the tables to a dedicated database in the SIMPLE recovery mode and to a separate set of disks not on the SAN.


Why would that affect the cluster's quorum drive?


I didn't have anything to do with this setup so I don't have a sufficient understanding of the details but our NetOps guys are apparently using the quorum drive to transfer data to our warm DR site. If the pipe between here and the DR site can't keep up, then the data on the quorum drive just gets larger and larger. There was some tipping point where if it got too far behind, it would go into a rather dedicated transfer mode and that just crushed the server when it happened. I use past tense because they supposedly fixed the problem but I'm not sure what they did to fix it other than getting a better pipe between us and the DR site.


--Jeff Moden
"RBAR is pronounced "ree-bar" and is a "Modenism" for "Row-By-Agonizing-Row".

First step towards the paradigm shift of writing Set Based code:
Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column."

(play on words) "Just because you CAN do something in T-SQL, doesn't mean you SHOULDN'T." --22 Aug 2013

Helpful Links:
How to post code problems
How to post performance problems
Post #1502405
Posted Monday, October 7, 2013 4:24 PM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 3:09 PM
Points: 40,204, Visits: 36,605
Jeff Moden (10/7/2013)
GilaMonster (10/7/2013)
Jeff Moden (10/5/2013)
I have a similar problem that turns out to be some rather inefficient code that truncates several very large tables and reloads ALL of the data from an AS 400 every bloody night. Folks are in the process of repairing the code for performance and I'm in the process of moving the tables to a dedicated database in the SIMPLE recovery mode and to a separate set of disks not on the SAN.


Why would that affect the cluster's quorum drive?


Because everything that changes int these tables ends up going to the quorum drive.


If it does someone has badly configured that cluster. There should be nothing from SQL Server on the quorum drive. I don't even know if the quorum drive can be marked as a dependency of SQL, it should be off limits to everything but the cluster management itself.

All that should be on the quorum drive are logs and a few files put down by the cluster installation, it should never be used for anything else.



Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

We walk in the dark places no others will enter
We stand on the bridge and no one may pass

Post #1502408
« Prev Topic | Next Topic »

Add to briefcase 123»»»

Permissions Expand / Collapse