Is there a way to compact the youtrack database (~/teamsysdata/)

I have a personal issue tracker on my development machine. I have maybe +/- 200 issues in there with only text (no attachements). All in all, I think the actual user content must be no more than 500kb. However over time my youtrack database has grown to almost 600mb. Aw. :-§

So that's like 99.99% overhead. That is inconvenient, especially to keep data backed up on line and such. So I wonder, is there a way to get rid of the cruft?

Also, I tried the backup function on the administration page of youtrack, but that fails with an error (so I have no idea of how big that would be):

java.lang.RuntimeException: java.lang.IllegalStateException: There's no current session to attach transient entity to.
    at jetbrains.charisma.main.AsyncBackupBean$
    at jetbrains.charisma.persistent.UserActionJob.execute(
    at jetbrains.exodus.core.execution.ThreadJobProcessor.executeJob(
    at jetbrains.exodus.core.execution.JobProcessorQueueAdapter.doExecuteJob(
    at jetbrains.exodus.core.execution.JobProcessorQueueAdapter.doJobs(
    at jetbrains.exodus.core.execution.ThreadJobProcessor$
Caused by: java.lang.IllegalStateException: There's no current session to attach transient entity to.
    at com.jetbrains.teamsys.dnq.database.TransientStoreUtil.reattach(
    at com.jetbrains.teamsys.dnq.association.PrimitiveAssociationSemantics.get(
    at com.jetbrains.teamsys.dnq.association.PrimitiveAssociationSemantics.get(
    at jetbrains.youtrack.ring.settings.RingConfigImpl.isEnabled(
    at jetbrains.youtrack.ring.maintenance.HubReadOnlyManager.isReadOnly(
    at jetbrains.youtrack.ring.maintenance.EmbeddedHubBackupable$EmbeddedHubBackupStrategy.beforeBackup(
    at jetbrains.exodus.util.BackupBean$1.beforeBackup(
    at jetbrains.exodus.util.CompressBackupUtil.backup(
    at jetbrains.charisma.main.AsyncBackupBean$
    ... 8 more


1 comment
Comment actions Permalink
Official comment


There seems to be a bug, could you please submit a support request , we'll investigate the issue deeper and could safely work with the sensitive database information.

Please sign in to leave a comment.