I have upgraded spicedb from 39 to 44.4
# spicedb
t
I have upgraded spicedb from 39 to 44.4 and in logs I can see there are continuous db call insertions to relation_tuple_transaction How to stop these calls and why is it happening
v
This is by design. A transaction heart beat was introduced recently. You don't want to disable, otherwise you'll regress performance - in clusters with low write RPS, permission checks will effectively incurr a performance overhead similar to
fully_consistent
.
It also fixes problems with the Watch API for postgres
If you still want to take the risk, you can disable it with setting
--enable-revision-heartbeat
to false
t
But won't DB will run out of memory if it runs every 5 seconds
v
How is Postgres going to run out of memory because a row is inserted every 5 seconds?
or are you referring to disk
t
Yes, I am concerned whether the existing storage limits will be crossed due to this insertion
v
that shouldn't be the case because SpiceDB will garbage collect from the transactions table. You can only have 24hours worth of transactions by default, and you can configure that window to be smaller
t
Got it that's nice. Can you point me to any documentation regarding this heartbeat and also how to configure this garbage window to be smaller Thanks
v
you can find documentation for the flags in
spicedb serve --help
. You can also find them in https://authzed.com/docs/spicedb/concepts/commands#flags
3 Views