Hi Siva, It may be wise to reach out to MarkLogic Support as well for more detailed guidance, but I can at least try to explain what the graph is showing you.
Your databases have a combined disk footprint of 450 Gb. If deleted fragments have been merged out fully, that is how much the actual data really needs for storage. However, MarkLogic needs additional space for normal maintenance. It needs extra space for merging. This is because of the MVCC approach where any update gets written as a new copy of the document, creating new so-called stand files as it goes. Old copies of documents get marked deleted, and are cleaned up in the background with merging. Multiple stands get merged into new ones while trimming off deleted fragments, after which the old stands are purged. That way MarkLogic can ensure it stays performant even after many updates. It also needs extra space for reindexing (in case index settings are changes after data was loaded). This causes new index files to be written, which replace existing ones as soon as re-indexation is done. Background maintenance like this can occur any time, and for multiple databases and forests at the same time. It could very well be that a forest is both reindexing and merging at the same time. If all databases are reindexing and merging at the same time, you need a lot of extra disk space until that finishes. The thumb rule is that you need roughly 1.5 times more free space than your forest data itself (see also http://docs.marklogic.com/guide/relnotes/other#id_43648). Your forest data is 450 Gb, so it would be best to have 675 Gb of free disk space. 549 Gb is less than that, so that is why you are seeing an exclamation mark next to the free space. Forest Reserve is the amount of free space you need to reserve to be able to merge all databases. See also http://docs.marklogic.com/guide/monitoring/dashboard#id_60621 Note though that these numbers don’t take MarkLogic backups into account. If you are running backup schedules, consider writing them to a separate mount, or offload them once finished. Cheers, Geert From: <general-boun...@developer.marklogic.com<mailto:general-boun...@developer.marklogic.com>> on behalf of "Mani, Sivasubramani (ELS)" <s.m...@elsevier.com<mailto:s.m...@elsevier.com>> Reply-To: MarkLogic Developer Discussion <general@developer.marklogic.com<mailto:general@developer.marklogic.com>> Date: Thursday, June 22, 2017 at 11:26 AM To: MarkLogic Developer Discussion <general@developer.marklogic.com<mailto:general@developer.marklogic.com>> Cc: ConSyn-Infosys-Support <consyn-infosys-supp...@reedelsevier.com<mailto:consyn-infosys-supp...@reedelsevier.com>> Subject: [MarkLogic Dev General] Regarding Marklogic space Hi Team, I am new to Mark Logic. In the Mark Logic Monitoring Dashboard one of my Mark Logic Node show’s critical disk space. My Free disk space is 549GB but show’s 9.8% capacity. What is meant by capacity here How capacity is arrived. If capacity is in critical it causes any problem to the node, if yes then how can we resolve this. Kindly help on this. [cid:image001.png@01D2EB42.1330F470] Thanks & Regards, Siva
_______________________________________________ General mailing list General@developer.marklogic.com Manage your subscription at: http://developer.marklogic.com/mailman/listinfo/general
