ngoDB shouldn't need much processing power when being used by Graylog.
>
> Are there any error messages in the logs of your MongoDB nodes? Are there
> any unusually large collections in the MongoDB database used by Graylog?
>
> Which MongoDB storage engine (MMAPv1, WiredTiger) are you u
Hello,
I am running the single node setup below:
Graylog 2.0.3
MongoDB 3.2.7
Elasticsearch 2.3.3
Red Hat Enterprise Linux Server 6.5
Java 8
NXlog and Graylog Collector Sidecar for reading from local logs
On average graylog is reading about 50 logs per second. MongoDB is not
being used for
Increasing the heap size on ES and Graylog respectively fixed the issue.
On Friday, July 8, 2016 at 11:07:46 AM UTC-5, Ariel Godinez wrote:
>
> After further investigation I think this was due to elasticsearch and
> graylog being overloaded. I have increased their heap sizes ac
After further investigation I think this was due to elasticsearch and
graylog being overloaded. I have increased their heap sizes accordingly and
will see how the system performs.
Ariel
On Wednesday, July 6, 2016 at 12:21:11 PM UTC-5, Ariel Godinez wrote:
>
> Hello,
>
> I've been u
Hello,
I've been using graylog for a couple weeks now and started to notice some
unusual behavior today. I am currently running a single node setup.
The Issue:
Every once in awhile I start to notice that that graylog is dragging quite
a bit (the loading spinner is persisting much longer than
system clock is off by a minute or so, the information in
>> MongoDB will be considered stale and the node is trying to re-register
>> itself.
>
>
>
> Cheers,
> Jochen
>
> On Monday, 20 June 2016 18:13:52 UTC+2, Ariel Godinez wrote:
>>
>> Hello,
>&g
Linux Server release 6.5 (Santiago)
Thanks,
Ariel Godinez
--
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 graylog2+unsubscr...@googlegroups.co
