Redistributing Shards across Index Nodes
Unlike archive nodes, which are sized according to the number of users, Index servers are sized according to the number of documents being processed. Note that a typical Index server with 32GB of RAM is sufficient to process 50 million documents, or approximately 25 million emails without indexing attachments. If you experience slowness in processing, this is likely due to loads placed on the Index server. Contact Support to assist with diagnosing the source of the slowness. Redistributing shards across the index nodes you have deployed could alleviate the problem.
NOTE
It is typical for each Index server to hold 8 “shards”. Each shard holds the indexes for a certain number of users. After adding an Index server, it is recommended to distribute the existing shards evenly across the existing and new Index (i.e. 4 shards on Index 1 and 4 shards on Index 2).
It is typical for each Index server to hold 8 “shards”. Each shard holds the indexes for a certain number of users. After adding an Index server, it is recommended to distribute the existing shards evenly across the existing and new Index (i.e. 4 shards on Index 1 and 4 shards on Index 2).
How to redistribute shards across index nodes
- Ssh into the existing solr node and stop services with this command:
service netmail stop - Manually move half the shards to the index path of the new solr node, which is /var/netmail/index by default. Place them directly beside the bin and logs folders. The data structure should go from this:
- To this:
- Start services on solr 1 with this command:
service netmail start - Restart services on solr 2 with this command:
service netmail restart - Go to the solr console IP:31000 and click Cloud.
- The new shard distribution for the “ma” collection displays.
