Yea, having exact dataDir as a system property is a flawed design dating back before distributed Solr… See https://issues.apache.org/jira/browse/SOLR-6671 <https://issues.apache.org/jira/browse/SOLR-6671> for my proposal to solve the user requirement of placing ALL data dirs on a separate volume. The patch is almost ready for commit…
Please review and comment :) -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com > 25. mai 2017 kl. 22.21 skrev Shawn Heisey <apa...@elyograg.org>: > > On 5/25/2017 2:05 AM, takumi yoshida wrote: >> I wounder if we add new parameter dataDir for collection CREATE >> command. There have been dataDir for ADDREPLICA command. So, if we add >> dataDir for CREATE too, it would be more easy to handle data directory >> when we make new collection with new disk or NFS, etc ... > > I'm with Erick. The danger of creating multiple cores on the same > server with exactly the same dataDir is simply too high. It doesn't > make sense to add a dataDir parameter to the Collections API CREATE. > > By editing core.properties files on an individual server after the > collection is created to add the dataDir property, and restarting Solr, > you can move a dataDir. The location would be relative to the place the > core.properties file is found. This could be dangerous, but done > correctly, would work. > > Thanks, > Shawn > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org > For additional commands, e-mail: dev-h...@lucene.apache.org >
