Hi @dmitry.s Our present disk space yeti uses on the server is full and I already inserted some empty disk. how should i go about this to make sure the files are not written to the new disk rather than the old
This question is not related to yeti. It is more about linux administration and as I know it is not enough just insert disk. So files will not be written to new disk.
Oh I thought after mounting the new disk I would need to change the directory at the postgresql. var/lib/postgresql.
Your intentions are not clear. In first message you asked how
to make sure the files are not written to the new disk
If you don’t want files to be written on new disk - it is enough to do nothing.
Oh please sorry it was a mistake from my end. what I meant is how to make sure the CDRs are now going to be written to the new disk after mounting
@dmitry.s any way to do this aside just changing the directory?
yeti does not write CDRs itself. it uses postgres database for that.
where this data will be physically stored depends solely from your postgres database configuration.
and it’s the database/linux administration question. not related to the yeti project at all.
the whole question sounds like: ‘how to move postgresql database to another drive?’
(answer example for it: https://dba.stackexchange.com/questions/28926/moving-postgresql-data-to-different-drive)
i can add that it’s safe to shutdown database for a short maintenance.
CDRs for active traffic will be stored in the in-memory retrying queue on the node and then be written after the DB reconnected.
1 Like