Hi Klaus,
unfortunately it's not that easy to calculate the exact disk space
requirement for the given numbers. For example your log messages could be
as small as a few bytes and as big as several kilobytes or even megabytes.
Additionally it's important how heterogenous the log messages are. If
Hi Jochen,
hi list,
first of all, thank you!
of course your're right, that the disk volume is not only depending on the
count of messages, the averge message size is important to. I will reme,ber
this!
BUT, *another Question*: How is the *relationship between* the *used space
from MongoDB (/v
Hi Klaus,
MongoDB is only used for configuration data (e. g. inputs configuration,
dashboards, streams, users, etc.) and to store index failures (i. e.
messages that couldn't be properly indexed into Elasticsearch because of a
index mapping conflict) and all processed log messages are being sto
Hi Jochen,
thank you for the explanation, BUT I have already a done a installation
with graylog, for testing and logs from 13 serves are logging into graylog,
ONLY over rsyslog and no webservers or something like that.
When I make a du -hs from Elasticsearch and from MongoDB, the pictures
seem
>
> Interesting - that ratio seems a little out of balance. 15M for ES for 13
> servers sounds quite light.
>
You can maybe get some more info on what is using space in Mongo doing the
> following:
>
On the server hosting mongodb:
mongo (This will enter the
Hi Klaus,
when you take a look into the "index_failures" collection, you should be
able to find the reason why those messages couldn't be properly indexed.
Cheers,
Jochen
On Thursday, 5 November 2015 14:01:26 UTC+1, kl...@tachtler.net wrote:
>
> Hi Jochen,
>
> thank you for the explanation, BU
Hi Jochen,
thank you for your help to understand graylog better. BUT first of all
graylog ist great and it helps me a lot in these first days of using it!
I looked into the System / Overview and got this:
Indexer failures
*No failed indexing attempts in the last 24 hours.*
I didn't miss any
Hi Werner,
i was doing this, like you said:
> use graylog2
switched to db graylog2
> db.index_failures.dataSize()
> db.dead_letters.dataSize()
> db.notifications.dataSize()
The output was always nothing!
I didn't miss any log messages, so this is NOT the problem.
I would understand better, h
You can manage size in three ways:
Retain a certain number of logs
Retain a certain period of logs
Retain a certain size of logs
Thus, how you manage it is up to you. In the config file you can choose which
of the above method you want to use, and set the thresholds.
So I would turn the questi
Hi Werner,
I was changed my setup like follwing:
My *retention strategy is now time* and the rotation is set to the default
*1d*.
-
rotation_strategy = time
-
elasticsearch_max_time_per_index = 1d
-
elasticsearch_max_number_of_indices = 14
So I
Hi Klaus,
I've heard from some users that their MongoDB server is using lots of space
for their journal. You might want to try to set smallfiles=true in the
MongoDB configuration file (see
https://docs.mongodb.org/v2.4/reference/configuration-options/#smallfiles)
to reduce the amount of disk s
* Jochen Schalanda [20151110 11:02]:
> I've heard from some users that their MongoDB server is using lots of space
> for their journal. You might want to try to set smallfiles=true in the
> MongoDB configuration file (see
> https://docs.mongodb.org/v2.4/reference/configuration-options/#smallfil
We enabled it on the appliances a while ago, should be the default now.
Cheers,
Marius
> It might make sense for this should be the default in the OVAs:
> otherwise MongoDB refuses to start with <3GB available.
>
> qvb
> --
> pica
>
--
You received this message because you are subscribed
Hi all,
can you take a look in mongo.log to check message error?
Alberto
On Tuesday, November 10, 2015 at 11:42:20 AM UTC+1, Joan Picanyol i Puig
wrote:
>
> * Jochen Schalanda > [20151110 11:02]:
> > I've heard from some users that their MongoDB server is using lots of
> space
> > for their jo
Hi Jochen,
thank you for your help, this is great that you give me the informations!
I set *smallfiles=true* in /etc/mongod.conf and I will watch the disk space
usage over the next days!
Thank you!
Klaus.
Am Dienstag, 10. November 2015 11:10:28 UTC+1 schrieb Jochen Schalanda:
>
> Hi Klaus,
>
>
Hi Alberto,
yes, I take a look in the /var/log/mongodb/mongod.log and there occured no
significant problems, I think:
- /var/log/mongodb/mongod.log -
2015-11-12T11:28:11.335+0100 [initandlisten] MongoDB starting : pid=27682
port=27017 dbpath=/var/lib/mongodb 64-bit host=server11.idmz.t
Hi Jochen,
thank you for the help!
Now, the used disk space is much more less, than without the
smallfiles=true setting, here the actual result after a few days:
# du -hs /var/lib/mongodb/
484M/var/lib/mongodb/
# du -hs /var/lib/elasticsearch/
12M/var/lib/elasticsearch/
Thank you!
Kla
17 matches
Mail list logo
