datomic 2022-08-23 | Slack Archive

timo09:08:02

Hi there, I am struggling with a 4TiB oracle-DB behind Datomic. I have a huge test-db as well, where I restored a backup into a fresh oracle-db and it only used 10% from the actual test-db. So my assumption is, that the prod-db is only a fraction after restore as well. Why is that? Is it possible to reduce the size of my prod-db without restoring and switching over? (Update: I've tried gc-storage but it didn't reduce the size of the test-db significantly)

rolt10:08:01

did you properly reclaim the space on the db side too ? This was my issue last time, the default reclaim behaviour was not adapted to datomic usage and we had to use a more aggressive one

jaret13:08:19

@U02F0C62TC1 is correct, @U4GEXTNGZ The most likely cause for disk size disparity pre and post restore is garbage. Datomic backups do not include garbage and reflect actual disk size.

timo13:08:47

ok thanks. that helps. any idea which word I need to shout at the oracle-admin for him to know which direction to go?

favila15:08:51

Is it the same issue as here? https://clojurians.slack.com/archives/C03RZMDSH/p1655301426331359

👍 1

favila15:08:46

There’s also gc-deleted-dbs. If the storage contains datomic databases that were deleted at the datomic level (d/delete-database), the segments from that database are not actually deleted from storage without an extra operation. https://docs.datomic.com/on-prem/operation/capacity.html#garbage-collection-deleted-production

2022-08-23

Channels