Jeff : Thanks. I have tried reload before but it is not reliable (atleast in 4.3.1). A few cores get initialized and few dont (show as just recovering or down) and hence had to move away from it. Is it a known issue in 4.3.1?
Shawn,Otis,Erick Yes I have reviewed the page before and have given 1/4 of my mem to JVM and the rest to RAM/Os Cache. (15 Gb heap and 45 G to rest. Totally 60G machine). I have also reviewed the tlog file and they are in the order of KB (4-10 or 30). I have SSD and the reads are hardly noticable (in the order of 100Kb during that time frame). I have also disabled swap on all machines Regarding firstSearcher, It is currently set to externalFileLoader. What is the use of first searcher? I havent played around with it Thanks Nitin On Mon, Feb 24, 2014 at 7:58 PM, Erick Erickson <erickerick...@gmail.com>wrote: > What is your firstSearcher set to in solrconfig.xml? If you're > doing something really crazy there that might be an issue. > > But I think Otis' suggestion is a lot more probable. What > are your autocommits configured to? > > Best, > Erick > > > On Mon, Feb 24, 2014 at 7:41 PM, Shawn Heisey <s...@elyograg.org> wrote: > > > > Hi > > > > > > I have a 4 node solrcloud cluster with more than 50 collections with 4 > > > shards each. Everytime I want to make a schema change, I upload configs > > to > > > zookeeper and then restart all nodes. However the restart of every node > > is > > > very slow and takes about 20-30 minutes per node. > > > > > > Is it recommended to make loadOnStartup=false and allow solrcloud to > lazy > > > load? Is there a way to make schema changes without restarting > solrcloud? > > > > I'm on my phone so getting a Url for you is hard. Search the wiki for > > SolrPerformanceProblems. There's a section there on slow startup. > > > > If that's not it, it's probably not enough RAM for the OS disk cache. > That > > is also discussed on that wiki page. > > > > Thanks, > > Shawn > > > > > > > > >
