I must tell you this. If I had someone who explained what I am going to explain to others my introduction to the VoIP world (several years ago) wouldn't be so hard as it was. The hardest thing when I started working with VoIP was following others' terms, some of them were invented (not technical terms); I was reading a lot and after my readings, I could understand what they wanted to say, even if they were using the wrong term.
I will try to explain in this article how VoIP works in terms of players, information flows and I will also explain to you some terms that are very common to use. In the end, I guess you will have a picture of who does what. I won't go into technical specifics such as SIP and RTP protocol details.
So after doing some readings, I saw that there are several advantages to using TokuDB over InnoDB when we are dealing with huge databases. The thing here is that using that TokuDB requires jemalloc to run. Since CentOS 7 and 8 are systemd enabled using the methods advertised on most websites won't work.
I will write here what I did to enable it,
After running successfully a medium-to-big cluster, one of your concerns is your database keeps growing. If you do not do anything, sooner than later there won't be a server that can host your FusionPBX database.
The good news about this is that it is very easy to know why the database grows so fast. It is logic, more customers, more calls, therefore, your database detailed record grows faster. In technical words, your v_xml_cdr table grows and grows.
Depending on the kind of customers you are hosting, CDR can be very valuable or depreciable. Depending on the country you are, by law, you may be required to store a CDR record somewhere. Somewhere not in your production database. So, your solution is to archive them. If someone asks for them, you will deal with that later.