We've seen the same thing on solr 7.5 by doing: - create a collection - add some data - stop solr on all servers - delete all contents of the solr node from zookeeper - start solr on all nodes - create a collection with the same name as in the first step
When doing this, solr wipes out the previous collection data and starts new. In our case, this was due to a startup script that checked for the existence of a collection and created it if non-existent. When not present in ZK, solr (as it should) didn't return that collection in it's list of collections so we created it... Possible that you have something similar in your workflow? Kyle On Wed, 9 Jan 2019 at 10:22, Erick Erickson <erickerick...@gmail.com> wrote: > Solr doesn't just remove directories, this is very likely > something in your environment that's doing this. > > In any case, there's no information here to help > diagnose. You must tell us _exactly_ what steps > you take in order to have any hope of helping. > > Best, > Erick > > On Wed, Jan 9, 2019 at 2:48 AM Yogendra Kumar Soni > <yogendra.ku...@dolcera.com> wrote: > > > > We are running a solr cloud cluster using solr 7.4 with 8 shards. When we > > started our solr cloud with a zookeeper node (without collections > directory > > but with only solr.xml and configs) our data directory containing > > core.propery and cores data becomes empty. > > > > > > > > > > -- > > *Thanks and Regards,* > > *Yogendra Kumar Soni* >
