32G for boot disk
ufm
46 Posts
April 12, 2020, 10:51 pmQuote from ufm on April 12, 2020, 10:51 pmHi!
Is it possible to install petasana on a 32G drive?
As I can see - more than 50G from 65G disk is free after installation.
WBR,
Fyodor.
Hi!
Is it possible to install petasana on a 32G drive?
As I can see - more than 50G from 65G disk is free after installation.
WBR,
Fyodor.
admin
2,930 Posts
April 13, 2020, 1:29 pmQuote from admin on April 13, 2020, 1:29 pmSpace will be taken by monitor databases, in case of cluster in recovery mode, they can grow quite large to keep track of recovery status/logs. 50 GB is not a lot. Beside storing stats, logs + we in the future we may add features that require more storage.
Space will be taken by monitor databases, in case of cluster in recovery mode, they can grow quite large to keep track of recovery status/logs. 50 GB is not a lot. Beside storing stats, logs + we in the future we may add features that require more storage.
ufm
46 Posts
April 13, 2020, 8:34 pmQuote from ufm on April 13, 2020, 8:34 pm
Quote from admin on April 13, 2020, 1:29 pm
Space will be taken by monitor databases, in case of cluster in recovery mode, they can grow quite large to keep track of recovery status/logs. 50 GB is not a lot. Beside storing stats, logs + we in the future we may add features that require more storage.
I have installed CEPH and no one of part of cluster not use more that 8G on boot disk. (Logs better store on external logger anyway). But I have 50 supermicro servers with DOM (special disk for boot) 32G. Their replacement is an expensive operation, both by money (each costs a little less than $ 200) and by time (servers are 150 kilometers from me in Datacenter). It will be very disappointing if only because of “maybe in the far future we will need more space” I will have to abandon the migration from raw CEPH to PetaSan. 🙁
Quote from admin on April 13, 2020, 1:29 pm
Space will be taken by monitor databases, in case of cluster in recovery mode, they can grow quite large to keep track of recovery status/logs. 50 GB is not a lot. Beside storing stats, logs + we in the future we may add features that require more storage.
I have installed CEPH and no one of part of cluster not use more that 8G on boot disk. (Logs better store on external logger anyway). But I have 50 supermicro servers with DOM (special disk for boot) 32G. Their replacement is an expensive operation, both by money (each costs a little less than $ 200) and by time (servers are 150 kilometers from me in Datacenter). It will be very disappointing if only because of “maybe in the far future we will need more space” I will have to abandon the migration from raw CEPH to PetaSan. 🙁
admin
2,930 Posts
April 13, 2020, 8:58 pmQuote from admin on April 13, 2020, 8:58 pmNo, as stated...the main reason as i pointed is the monitor database, it can reach 50GB during recovery as it records all cluster changes, once the cluster is healthy, it will shrink again.
No, as stated...the main reason as i pointed is the monitor database, it can reach 50GB during recovery as it records all cluster changes, once the cluster is healthy, it will shrink again.
32G for boot disk
ufm
46 Posts
Quote from ufm on April 12, 2020, 10:51 pmHi!
Is it possible to install petasana on a 32G drive?
As I can see - more than 50G from 65G disk is free after installation.
WBR,
Fyodor.
Hi!
Is it possible to install petasana on a 32G drive?
As I can see - more than 50G from 65G disk is free after installation.
WBR,
Fyodor.
admin
2,930 Posts
Quote from admin on April 13, 2020, 1:29 pmSpace will be taken by monitor databases, in case of cluster in recovery mode, they can grow quite large to keep track of recovery status/logs. 50 GB is not a lot. Beside storing stats, logs + we in the future we may add features that require more storage.
Space will be taken by monitor databases, in case of cluster in recovery mode, they can grow quite large to keep track of recovery status/logs. 50 GB is not a lot. Beside storing stats, logs + we in the future we may add features that require more storage.
ufm
46 Posts
Quote from ufm on April 13, 2020, 8:34 pmQuote from admin on April 13, 2020, 1:29 pmSpace will be taken by monitor databases, in case of cluster in recovery mode, they can grow quite large to keep track of recovery status/logs. 50 GB is not a lot. Beside storing stats, logs + we in the future we may add features that require more storage.
I have installed CEPH and no one of part of cluster not use more that 8G on boot disk. (Logs better store on external logger anyway). But I have 50 supermicro servers with DOM (special disk for boot) 32G. Their replacement is an expensive operation, both by money (each costs a little less than $ 200) and by time (servers are 150 kilometers from me in Datacenter). It will be very disappointing if only because of “maybe in the far future we will need more space” I will have to abandon the migration from raw CEPH to PetaSan. 🙁
Quote from admin on April 13, 2020, 1:29 pmSpace will be taken by monitor databases, in case of cluster in recovery mode, they can grow quite large to keep track of recovery status/logs. 50 GB is not a lot. Beside storing stats, logs + we in the future we may add features that require more storage.
I have installed CEPH and no one of part of cluster not use more that 8G on boot disk. (Logs better store on external logger anyway). But I have 50 supermicro servers with DOM (special disk for boot) 32G. Their replacement is an expensive operation, both by money (each costs a little less than $ 200) and by time (servers are 150 kilometers from me in Datacenter). It will be very disappointing if only because of “maybe in the far future we will need more space” I will have to abandon the migration from raw CEPH to PetaSan. 🙁
admin
2,930 Posts
Quote from admin on April 13, 2020, 8:58 pmNo, as stated...the main reason as i pointed is the monitor database, it can reach 50GB during recovery as it records all cluster changes, once the cluster is healthy, it will shrink again.
No, as stated...the main reason as i pointed is the monitor database, it can reach 50GB during recovery as it records all cluster changes, once the cluster is healthy, it will shrink again.