Thanks Per, would the first approach involve restarting Solr? Thanks Mark, that's great, Ill try checkout and apply patches from ticket to understand further. The reason we would like to avoid Zookeeper are * due to lack of knowledge. * the amount of work/scripting for developers per module and release documentation. * the extra steps of patching ZK nodes for QA and operations.
ZkCLI is a nice tool, but then instead of interacting with one service over HTTP, the application needs: * extra jar files * know ZK hostname/IP and port (different in each dev/qa/systest/accept/production environment), which is per module a one to much configuration step. On Thu, Jan 24, 2013 at 7:18 PM, Mark Miller <markrmil...@gmail.com> wrote: > > On Jan 24, 2013, at 10:02 AM, Fadi Mohsen <fadi.moh...@gmail.com> wrote: > > > Hi, We would like to use Solr to index statistics from any Java module in > > our production environment. > > > > Applications have to can create collections and index data on demand, so > my > > initial thought is to use different HTTP methods to accomplish a > collection > > in cluster and then right away start HTTP POST documents, but the issue > > here is the schema.xml. > > Is it possible to HTTP POST the schema via Solr to Zookeeper? > > I've done some work towards this at > https://issues.apache.org/jira/browse/SOLR-4193 > > > > > Or do I have to know about other service host/IP than SOLR, such as > > ZooKeeper (wanted to understand whether there is a way to avoid knowing > > about zookeeper in production.)? > > I wouldn't try to avoid it - it's probably simpler to deal with than you > think. > > It's also pretty easy to use > http://wiki.apache.org/solr/SolrCloud#Command_Line_Util to upload a new > schema.xml - then just Collections API reload command. Two lines in a > script. > > - Mark > >
