AnsweredAssumed Answered

Alfresco 3.4d - Running out of disk space

Question asked by varunv on May 14, 2012
Latest reply on Jun 14, 2012 by shmoula
Hi,

We are running the community edition of Alfresco 3.4d and we are noticing that after posting around 100 documents of size 22K through the webservice interface (individually - one file is being sent at a time), the machine is running out of disk space after 2 - 3 hours. The current disk size on the machine is 60GB and 6GB RAM. From investigation we noticed that the alf_data size is around 2.9GB and the index is 1.9GB.  Also, the CPU is at 100% the whole time ater the documents are added. 
The content store mainly contains PDF files of about 20KB and that there about 125,000 of them.

The main folder increasing in size is /alf_data/lucene-indexes/workspace/SpacesStore/.

Our JVM Startup configuration

 
-server -d64 -Xss1M -Xms2G -Xmx4G -XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:NewSize=1G -XX:MaxPermSize=256M -XX:CMSInitiatingOccupancyFraction=80 -XX:+UseParNewGC
Some information from our repository configuration is as below.

index.recovery.mode=VALIDATE
#
# Properties for merge (not this does not affect the final index segment which will be optimised)
# Max merge docs only applies to the merge process not the resulting index which will be optimised.
#
lucene.indexer.mergerMaxMergeDocs=1000000
lucene.indexer.mergerMergeFactor=9
lucene.indexer.mergerMergeBlockingFactor=1
lucene.indexer.mergerMaxBufferedDocs=-1
lucene.indexer.mergerRamBufferSizeMb=16
#
# Properties for delta indexes (not this does not affect the final index segment which will be optimised)
# Max merge docs only applies to the index building process not the resulting index which will be optimised.
#
lucene.indexer.writerMaxMergeDocs=1000000
lucene.indexer.writerMergeFactor=9
lucene.indexer.writerMaxBufferedDocs=-1
lucene.indexer.writerRamBufferSizeMb=16
#
# Target number of indexes and deltas in the overall index and what index size to merge in memory
#
lucene.indexer.mergerTargetIndexCount=5
lucene.indexer.mergerTargetOverlayCount=5
lucene.indexer.mergerTargetOverlaysBlockingFactor=1
lucene.indexer.maxDocsForInMemoryMerge=10000
lucene.indexer.maxRamInMbForInMemoryMerge=16
lucene.indexer.maxDocsForInMemoryIndex=10000
lucene.indexer.maxRamInMbForInMemoryIndex=16


Any input to help resove this issue would be appreciated.

Please let us know if you need further information.

Thanks
Varun

Outcomes