How to cut the system log in mongodb

Mongodb in how to cut system logs, many novices are not very clear about this, in order to help you solve this problem, the following editor will explain in detail for you, people with this need can come to learn, I hope you can gain something.

When mongodb sharding is done, when the mongos routing service is enabled, we will specify a location for storing logs:

Mongos-- configdb 127.0.0.1 logpath / var/log/mongodb/mongos.log-- pidfilepath / var/run/mongodb/mongos.pid-- logappend-- logRotate reopen-- fork

Above we specify that the log is stored in the / var/log/mongodb/mongos.log file. When the system has a large amount of data and runs for a long time, the mongos.log file will become several gigabytes in size, which will definitely affect the performance of mongos routing.

In this case, we can use the system's logrotate log auto-slicing service to change the size of the mongos.log file, go to the cd / etc/logrotate.d/ directory, create a file: touch mongos, and edit and add the following:

/ var/log/mongodb/mongos.log {rotate 1 daily dateext size 200m postrotate / bin/kill-SIGUSR1 `cat / var/run/mongodb/mongos.pid 2 > / dev/ null`2 > / dev/null | | true endscript}

A brief description of the above configuration:

Size: specifies that mongos.log files are automatically cut when they exceed 200m

Dateext: specifies how backup files are named when cutting files

Rotate 5: five archive logs will be stored at a time. For the sixth archive, the oldest archive will be deleted.

Daily: log files will be polled by day

Postrotate/endscript: when the other commands are executed, execute the commands in this one

Is it helpful for you to read the above content? If you want to know more about the relevant knowledge or read more related articles, please follow the industry information channel, thank you for your support.