It will only prevent you when configured correctly, you have to look at the size of your indexes, and define your strategy based on the usage.
You could use a plugin like ELASTICHQ for elastic to have a better look at what your ES servers are doing. On Wednesday, December 9, 2015 at 10:48:14 AM UTC+1, Per Erik Nordlien wrote: > > Dear all. > > I have 2 separate Graylog installations going based on the downloadable > OVA. I have successfully upgraded them to the latest version. They run fine > for some time but, then unassigned shards starts to pop up and they run out > of disk. I have a hard time getting any retention scheme to work. I assume > that any "sudo graylog-ctl set-retention" command would help me prevent > that Graylog run out of disk space. I have tried many commands to resolve > the unassigned shards issue but, when it comes to curl commands I have no > idea what I'm doing, what to check for or even if I'm using them correct. > > First question: How do I resolve unassigned shards? Is there some dummy > guide out there somewhere that could help me through it? > > Second question: How do I get a retention scheme working? Is it correct > that it would prevent me from running out of disk? > > Regards > -- You received this message because you are subscribed to the Google Groups "Graylog Users" 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/graylog2/213b4452-4530-458c-abe3-d80415d0fc7d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
