: If you are not searching against your master, and you shouldn't (and : it sounds like you aren't), then you don't have to worry about : disabling caches - they will just remain empty. You could comment : them out, but I think that won't actually disable them.
FWIW: what i generall advocate is that even if you have a machine that *should* never get queries (ie: master, repeater, backup, ... whatever) it's still a good idea to leave small caching enabled on that machine. the reason being that *IF* some rogue client mistakenly starts sending requests to this server they are not suppose to be sending requests to, then i would rather those requests get cached to help reduce the likelyood of the machine rolling over and dieing under load -- but i advise disabling all the autowarming and any explicit newSearcher warming you might normally confugre so that if there is a blip and this situation does happen, then newSearcher events aren't delayed dealing with caching warming over and over again even long after the rogue client gets stopped. Related suggestion: disable all the requestHandler names you clients nomraly query in your "master" solrconfig.xml, and only expose on using a really bizare unlikely name so you have someway to query that index for debugging ... that way if clients that normally query "http://slave:8983/solr/products/search?q=..."; get misconfigured to hit "http://master:8983/solr/products/search?q=..."; they'll get a 404. but you can still use "http://master:8983/solr/products/secret-debug-search?q=..."; as needed. -Hoss
