Hello,
I Googled for a like problem but didn't get any hits. If this has already
been answered please point me to that post.
We are having a problem with our MySQL database used for Artifactory where
it is constantly increasing in size by gigabytes per day. The current size
of the "${ArtifactoryHome}/data" directory is over 200GB yet there are only
74K artifacts stored. A full backup is less than 38GB.
We are using Artifactory v2.6.1 with MySQL v5.5.34 on a Windows 2003 R2 SP2
with 3.5GB memory and 2 Xeon CPUs. MySQL storage was setup according to
http://www.jfrog.com/confluence/display/RTF2X/Changing+the+Default+Storage
and
http://www.jfrog.com/confluence/display/RTF2X/Running+Artifactory+on+MySQL.
The artifactory.system.properties has
"artifactory.jcr.configDir=repo/filesystem-mysql" and the
./etc/repo/filesystem-mysql/repo.xml file was updated with the MySQL
connection information.
We had an instance of Artifactory running on an identical server but using
the default Derby Db. Last November we did a full system export from that
instance then imported the export into the new instance using MySQL. The
new instance using MySQL is behaving like the instance that was using Derby
where the "data" directory constantly increases in size. The only way to
prevent the disk from becoming full is to do a full system export then
import the system which reduces the "data" directory to less than 40GB.
The Artifactory local snapshot repos are set to unique snapshots and store
3 snapshots. I suspect that when new snapshots are deployed that the
storage for the deleted snapshot is not being reclaimed in the database.
Is it possible that there is a setting that was imported from the system
import that makes MySQL act like Derby? Should derby specific props that
were included by default in the artifactory.system.properties file be
deleted/commented out? Is there something we can run within MySQL that will
reclaim this space? We haven't tried optimizing any of the tables yet.
Should that be attempted?
We plan to upgrade to the latest version of Artifactory this year but right
now need to better understand how to stop the MySQL db from filling the
disk. Any help or suggestions are appreciated.
Regards,
Ken
------------------------------------------------------------------------------
Subversion Kills Productivity. Get off Subversion & Make the Move to Perforce.
With Perforce, you get hassle-free workflows. Merge that actually works.
Faster operations. Version large binaries. Built-in WAN optimization and the
freedom to use Git, Perforce or both. Make the move to Perforce.
http://pubads.g.doubleclick.net/gampad/clk?id=122218951&iu=/4140/ostg.clktrk
_______________________________________________
Artifactory-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
