MongoDB – Production Readiness

https://docs.mongodb.com/manual/sharding/ – To be discussed and agreed on https://docs.mongodb.com/manual/replication/ – Must
https://scalegrid.io/blog/should-you-enable-mongodb-journalling/ – Recommended
Backup and Recovery – Must

How Journaling works?
https://www.mongodb.com/blog/post/how-mongodbs-journaling-works

Advertisements

Elasticsearch – Pinpointing problematic shards

https://www.datadoghq.com/blog/elasticsearch-unassigned-shards/#pinpointing-problematic-shards

The master node may not be able to assign shards if there are not enough nodes with sufficient disk space (it will not assign shards to nodes that have over 85 percent disk in use). Once a node has reached this level of disk usage, or what Elasticsearch calls a “low disk watermark”, it will not be assigned more shards.

Keep an eye on disk space

Network Time Protocol (NTP)

In Unix/Linux we need to make sure that servers are configured to sync with time server to have consistent time on all servers. Otherwise, it is tough to map events across systems.

>ntpstat
>ntpq -pn
>timedatectl status

To make sure that ntp is configured to start with every system restart
>chkconfig –list ntpd

Reference:
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/6/html/deployment_guide/s1-checking_the_status_of_ntp

https://www.cyberciti.biz/faq/linux-unix-bsd-is-ntp-client-working/