Description of problem: It's suggested that graphite/carbon data stored in `/var/lib/carbon` is placed on a separate disk device[1]. When a cluster is unmanaged[2], all data from graphite related to cluster is moved from `/var/lib/carbon/whisper/tendrl/clusters/<cluster_id>` to `/usr/share/tendrl/graphite/archive/clusters/<cluster_id>_<timestamp>`. This is very demanding on disk utilization as these data could be very large and the disk space for carbon data is preallocated by WA right after cluster is created. In documentation there should be provided information about this behaviour during cluster unmanage and that the archived data will end up on root disk partition after unmanage task is completed although graphite/carbon could be located on a separate disk. [1] https://github.com/Tendrl/documentation/wiki/Tendrl-release-v1.6.2-(install-guide)#tendrl-server-system-requirements [2] https://bugzilla.redhat.com/show_bug.cgi?id=1526338
* Is this statement correct? * Are there any plans about changing this behaviour?
Created attachment 1428802 [details] Graphite data archived in same disk
I have modified the logic to copy the graphite data into same disk where graphite data are stored
@fbalak, Please take a look at https://bugzilla.redhat.com/show_bug.cgi?id=1571906. Hence this bug is not relevant any more and we should consider closing this bug.
(In reply to Nishanth Thomas from comment #5) > @fbalak, Please take a look at > https://bugzilla.redhat.com/show_bug.cgi?id=1571906. Hence this bug is not > relevant any more and we should consider closing this bug. This is a good point, but instead of closing this BZ, we may need to update it with the new expected behavior. One should still be aware that the archival is happening, where the files are stored and how much space it could take.
Data is archived at: '/var/lib/carbon/whisper/tendrl/' where `/var/lib/carbon` is mounted on a separate disk as per the recommendation. I don't think size need not be specified here as it depends on the size of the cluster. One could look at the hw sizing guide for the approximate calculation.
I would suggest to use full path of the cluster archives, which is: ``` /var/lib/carbon/whisper/tendrl/archive/clusters ``` unless WA can archive something else in /var/lib/carbon/whisper/tendrl/archive/ directory I'm not aware off. Nishant, could you verify that there is nothing else but clusters archived there?
(In reply to Martin Bukatovic from comment #10) > I would suggest to use full path of the cluster archives, which is: > > ``` > /var/lib/carbon/whisper/tendrl/archive/clusters > ``` > > unless WA can archive something else in > /var/lib/carbon/whisper/tendrl/archive/ > directory I'm not aware off. > > Nishant, could you verify that there is nothing else but clusters archived > there? Martin, Appended the full path of cluster archives: https://access.qa.redhat.com/documentation/en-us/red_hat_gluster_storage/3.4/html-single/monitoring_guide/#graphite_and_carbon_data_archival If Nishanth confirms otherwise, we will discard "cluster"
There is nothing else archived into `/var/lib/carbon/whisper/tendrl/archive` directory.
Based on info from Nishanth (comment 12), we don't need to change the text further. Moving to VERIFIED.
Fixing status.