mongodb - Different indexes on different replica set members -


as part of our mongo cluster, have hidden node analytics people use reporting. queries quite bit different ones our main application optimized for.

we can improve performance of queries quite dramatically adding indexes, relatively expensive compute, , take fair amount of memory. indexes should not used of queries running on our primary , secondary members, seems bit silly spend time , memory on main replica set members compute , keep reporting indexes in memory.

is there way create index exists on single replica set member? there way tell primary , secondary nodes not compute or store indexes know not use?

yes - can use variation on strategy used creating new index in replica set without down time. require hidden member taken off-line while index(es) created.

here link strategy: http://docs.mongodb.org/manual/tutorial/build-indexes-on-replica-sets/#procedure

in case take hidden member off-line , restart in standalone mode (remove --replset option , use different port number). once member isolated can adjust indexes (remove un-needed ones , add new ones). once indexes done being created restart member old port , --replset option.

the hidden member resync replica set , set.


Comments

Popular posts from this blog

linux - xterm copying to CLIPBOARD using copy-selection causes automatic updating of CLIPBOARD upon mouse selection -

c++ - qgraphicsview horizontal scrolling always has a vertical delta -