Hi Jochen,
Thanks for answers.
I'll try different scenarios. iptables seems easiest solution ;)
On Sunday, November 2, 2014 1:05:57 PM UTC+2, Jochen Schalanda wrote:
>
> Hi Dmitri,
>
> But how to upgrade radio without loosing any messages?
>>
>
> There are several ways to upgrade Graylog2 Radio
Hi Seby,
Am Sonntag, 2. November 2014 09:15:33 UTC+1 schrieb Seby Francis:
>
> We have a cluster of graylog2 servers (3 instances on aws) configured and
> I see the message_cache_spool_dir is getting filled up. Not sure what to
> change.
>
Unfortunately the off-heap message cache is currently u
Hi Marty,
this is a bug in Graylog2. The next release (which is due real sonn™ now)
will include a fix for this.
Cheers,
Jochen
--
You received this message because you are subscribed to the Google Groups
"graylog2" group.
To unsubscribe from this group and stop receiving emails from it, sen
Hi Dmitri,
But how to upgrade radio without loosing any messages?
>
There are several ways to upgrade Graylog2 Radio without losing messages:
- If your clients can buffer log messages, just pause the sending logs
to Graylog2 Radio, upgrade it, and resume the sending of logs to Graylog2
Hi guys,
We have a cluster of graylog2 servers (3 instances on aws) configured and I
see the message_cache_spool_dir is getting filled up. Not sure what to
change. I see this on graylog2 master host as well. Here is the snippet of
diskusage:
[root@2-graylog2 ~]# df -h
Filesystem Size Use