Sisense Builds consumes too much Disk SpaceAnswered
Every morning our server's disk space gets too low, I suspect this is because of the scheduled builds that run at night and early morning, for example, this morning, we only have 8.57 gb free space in the C drive, then, we reboot the server, the C drive space is back to 48.6 gb.
Is this the normal behavior of Sisense or you think there are other factors? Is there a way to free up space without rebooting the server?
Your replies are appreciated. Thank you very much! ~~
there could be two reasons behind this:
1. Logs - if you go to c:\ProgramData\Sisense\ and then either Logs or PrismWeb\Logs or PrismServer\PrismServerLogs - there you will find lots of old logs. You may want to clear that.
2. Failed ElastiCube builds - on rare occasions, a failed build can create a Copy of ElastiCube data and keep it on your disk until you delete it. if you go to c:\programdata\sisense\prismserver\elasticubedata - there you should see a folder for each ElastiCube with name and last processing date. If you have multiple folders for one ElastiCube, you can safely delete all except for the most recent one. Older versions are not used anyway and this can save a lot of disk space.
Finally you can launch Sisense Server Console and in settings there
you can change storage path in here to larger disk other than C:
Hope this helps!
Thanks Michael! But why does it clear up during reboots?0
It should not really(maybe someone from Sisense can shed some light if it does). The other factor could mongodb which is used behind the scenes in Sisense. The nature of this database is that as it continues running, the overall speed is improving but a lot of disk space is consumed. It might be that after restarting mongo releases a lot disk space. Those are speculations to be honest, maybe you can rise a ticket for the support, they will know better what could be the reason.
I will check on mongoDB. Thank you very much Michael! Really appreciate it. Regards!0
Post is closed for comments.