I now know that Marvel creates a lot of data per day of monitoring - in our case around 1Gb.
What I'm just starting to get my head around is the imbalance of disk usage that this caused on my 5 node cluster. I've now removed Marvel and deleted the indexes for now (great tool, but I don't have the disk space to spare on this proof of concept) and my disk usage for the 12 months of rsyslog data has equalised across all the nodes in my cluster. When the Marvel data was sitting there, not only was I using far too much disk space, but I was also seeing significant differences between nodes. At least one node would be using nearly all of the 32Gb, where other nodes would sit at half that or even less. Is there something intrinsically different about Marvel's indexes that makes them prone to such wild differences? Thanks Duncan -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/7c7d7fb3-a704-4ea5-a74d-efa01f1fa11d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
