Hi,

I am using solr to store data of multiple applications, currently routing one 
application data to one shard using compositeId routing with app name as the 
shard key 

Ex: myapp!docid

however I observed recently one of the app data seems to be growing 
significantly and is expected to quadruple in coming months, so I wanted to try 
multi-tenant approach of using different shard key

Ex: myapp/2!docid

so that data is routed to 1/4 of shards instead of single shard

There are lot of joins and ngroups in our app, what would be the impact of 
this, since changing the shard key for the app would spread docs across 
multiple shards, do these still work ?
All our apps are using same collection, does using a different shard key for 
one of the app requires re-indexing other apps data ? 
Ex: all existing apps using app name as shard key and now for one of the app we 
planning to change it to app name/2 to leverage multiple shards for that app

Also what's the difference between solr shard and solr core, on some of the 
blogs I read, for joins and ngroups to work the documents need to be colocated 
on same core or vm. so I am assuming core here means shard.

Thank you

Reply via email to