Dang it. I know better than that, but I was blindly following the docs. Which means the docs have a problem, since they are recommending something that should not be recommended.
Putting variable data on a different volume is very common. Official support for that goes at least as far back as Unix V7 (1979), with /var. It should be easy to do in Solr. I expected to see the shard names as directories under /solr/data, but I now remember that I need to set that with a variable. Time to delete everything and rebuild everything again. wunder Walter Underwood wun...@wunderwood.org http://observer.wunderwood.org/ (my blog) > On Feb 24, 2017, at 8:30 AM, Shawn Heisey <apa...@elyograg.org> wrote: > > On 2/23/2017 6:41 PM, Walter Underwood wrote: >> I did this in the solrconfig.xml for both collections (tutors and >> questions). >> >> <dataDir>/solr/data</dataDir> >> >> I deleted the old collection indexes, reloaded, restarted, and created a new >> collection for “tutors". And I see this on the disk. > > Setting dataDir in solrconfig.xml, especially to an absolute path like > that, is generally not a good idea. It's VERY bad if that config will > be used by multiple cores. The best place to do it is in > core.properties, so it's part of the core definition and independent of > config/schema. IMHO it's best to make it a relative path. Below is a > core.properties file from my dev system running 6.3.0, in a > "cores/sparkinc_0" directory under the solr home. > > I do not see anything broken in the directory listings you provided. > What do you see that is misplaced? > > With SolrCloud, I wouldn't be setting dataDir *at all* -- I would let > Solr handle that, mostly because the config for SolrCloud is not on the > disk and therefore dataDir doesn't need to be separated from instanceDir. > > #Written by CorePropertiesLocator > #Mon Feb 06 19:24:18 UTC 2017 > name=sparkinclive > loadonStartup=false > dataDir=../../data/sparkinc_0 > transient=false > > Thanks, > Shawn >
