{"id":2585,"date":"2018-01-12T17:23:27","date_gmt":"2018-01-12T14:23:27","guid":{"rendered":"https:\/\/www.howtoforge.com\/tutorial\/deploying-mongodb-sharded-cluster-on-centos-7\/"},"modified":"2018-01-12T17:23:27","modified_gmt":"2018-01-12T14:23:27","slug":"how-to-deploy-a-mongodb-sharded-cluster-on-centos-7","status":"publish","type":"post","link":"https:\/\/afaghhosting.net\/blog\/how-to-deploy-a-mongodb-sharded-cluster-on-centos-7\/","title":{"rendered":"How to Deploy a MongoDB Sharded Cluster on CentOS 7"},"content":{"rendered":"

Sharding<\/strong> is a MongoDB process to store data-set across different machines. It allows you to perform a horizontal scale of data and to partition all data across independent instances. Sharding allows you to add more machines based on data growth to your stack.<\/p>\n

Sharding and Replication<\/h2>\n

Let’s make it simple. When you have collections of music, ‘Sharding’ will save and keep your music collections in different folders on different instances or replica sets while ‘Replication’ is just syncing your music collections to other instances.<\/p>\n

Three Sharding Components<\/h2>\n

Shard<\/strong> – Used to store all data. And in a production environment, each shard is replica sets. Provides high-availability and data consistency.<\/p>\n

Config Server<\/strong> – Used to store cluster metadata, and contains a mapping of cluster data set and shards. This data is used by mongos\/query server to deliver operations. It’s recommended to use more than 3 instances in production.<\/p>\n

Mongos\/Query Router<\/strong> – This is just mongo instances running as application interfaces. The application will make requests to the ‘mongos’ instance, and then ‘mongos’ will deliver the requests using shard key to the shards replica sets.<\/p>\n

Prerequisites
<\/strong><\/h2>\n