Thanks Shawn. I'm using 2 level composite id routing right now. These are all Used Cars listings and all search queries always have car year and make in the search criteria - hence that made sense to have Year+Make as level 1 in the composite id. Beyond that the second level composite id is based on about 8 car attributes and that means all listings for a similar type of car and listings of any car are grouped together and co-located in the SlorCloud. Even with this there is still an imbalance in the cluster - as certain car makes are popular and there are more listings for such cars that go the same shard. Will splitting these up with the existing set of hardware help at all?
-- View this message in context: http://lucene.472066.n3.nabble.com/SolrCloud-Scale-Struggle-tp4150592p4150811.html Sent from the Solr - User mailing list archive at Nabble.com.
