I'm pretty sure there's been some hardening of deleting nodes/collections to deal with nodes in a "bad" state, I'm pretty sure they're available in 4.3. Not guaranteeing that this would solve your problem, but it's probably worth looking at the CHANGES.txt for 4.3 to see if it's worth exploring....
Best Erick On Fri, Apr 19, 2013 at 2:39 PM, Nate Fox <n...@neogov.com> wrote: > I've used zookeeper's cli to do this. I doubt its the right way and I have > no idea if it'll work for clusterstate.json, but it seems to work for > certain things. > > cd /opt/zookeeper/bin > ./zkCli.sh -server 127.0.0.1:2183 set /configs/collection1/schema.xml "`cat > /tmp/newschema.xml`" > sleep 10 # give a lil time to get pushed out > curl " > http://localhost:8080/solr/admin/cores?wt=json&action=RELOAD&core=collection1 > " > > This is on zk 3.4.5 > > > > -- > Nate Fox > Sr Systems Engineer > > o: 310.658.5775 > m: 714.248.5350 > > Follow us @NEOGOV <http://twitter.com/NEOGOV> and on > Facebook<http://www.facebook.com/neogov> > > NEOGOV <http://www.neogov.com/> is among the top fastest growing software > companies in the USA, recognized by Inc 500|5000, Deloitte Fast 500, and > the LA Business Journal. We are > hiring!<http://www.neogov.com/#/company/careers> > > > > On Fri, Apr 19, 2013 at 11:30 AM, Mingfeng Yang <mfy...@wisewindow.com>wrote: > >> Right. I am wondering if/how we can download a specific file from the >> zookeeper, modify it and then upload to rewrite it. Anyone ? >> >> Thanks, >> Ming >> >> >> On Fri, Apr 19, 2013 at 10:53 AM, Michael Della Bitta < >> michael.della.bi...@appinions.com> wrote: >> >> > I would like to know the answer to this as well. >> > >> > Michael Della Bitta >> > >> > ------------------------------------------------ >> > Appinions >> > 18 East 41st Street, 2nd Floor >> > New York, NY 10017-6271 >> > >> > www.appinions.com >> > >> > Where Influence Isn’t a Game >> > >> > >> > On Thu, Apr 18, 2013 at 8:15 PM, Manuel Le Normand >> > <manuel.lenorm...@gmail.com> wrote: >> > > Hello, >> > > After creating a distributed collection on several different servers I >> > > sometimes get to deal with failing servers (cores appear "not >> available" >> > = >> > > grey) or failing cores ("Down / unable to recover" = brown / red). >> > > In case i wish to delete this errorneous collection (through collection >> > > API) only the "green" nodes get erased, leaving a meaningless >> unavailable >> > > collection in the clusterstate.json. >> > > >> > > Is there any way to edit explicitly the clusterstate.json? If not, how >> > do i >> > > update it so the collection as above gets deleted? >> > > >> > > Cheers, >> > > Manu >> > >>
