I'd guess user error in the absence of stronger information. No docs added, no optimized kicked off, no replication and I can't think of any reason the index size should increase.
Erick 2011/9/15 Yury Kats <yuryk...@yahoo.com>: > On 9/14/2011 2:36 PM, Erick Erickson wrote: >> What is the machine used for? Was your user looking at >> a master? Slave? Something used for both? > > Stand-alone machine with multiple Solr cores. No replication. > >> Measuring the size of all the files in the index? Or looking >> at memory? > > Disk space. > >> The index files shouldn't be getting bigger unless there >> were indexing operations going on. > > That's what I thought. > >> Is it at all possible that >> DIH was configured to run automatically (or any other >> indexing job for that matter) and your user didn't realize it? > > There's no DIH, but there is a custom app that submit docs > for indexing via SolrJ. Supposedly, Solr logs were not showing > any updates over night, so the assumption was that no new docs > were added. > > I'd write it off as a user error, but wanted to double check with > the community that no other internal Solr/Lucene task can change the index > file size in the absence of submits. >
