On 6/2/2014 2:21 PM, Marc Campeau wrote: > I notice I have this in the logs when I start SOLR for default example (I > had the same with my own connection) > > 21242 [coreZkRegister-1-thread-1] INFO > org.apache.solr.cloud.ShardLeaderElectionContext – Enough replicas found > to continue. > 21242 [coreZkRegister-1-thread-1] INFO > org.apache.solr.cloud.ShardLeaderElectionContext – I may be the new > leader - try and sync > 21242 [coreZkRegister-1-thread-1] INFO org.apache.solr.cloud.SyncStrategy > – Sync replicas to http://192.168.150.90:8983/solr/collection1/ > 21243 [coreZkRegister-1-thread-1] ERROR org.apache.solr.cloud.SyncStrategy > – No UpdateLog found - cannot sync > 21243 [coreZkRegister-1-thread-1] INFO > org.apache.solr.cloud.ShardLeaderElectionContext – We failed sync, but we > have no versions - we can't sync in that case - we were active before, so > become leader anyway > 21243 [coreZkRegister-1-thread-1] INFO > org.apache.solr.cloud.ShardLeaderElectionContext – I am the new leader: > http://192.168.150.90:8983/solr/collection1/ shard1 > 21243 [coreZkRegister-1-thread-1] INFO > org.apache.solr.common.cloud.SolrZkClient – makePath: > /collections/collection1/leaders/shard1
The "No UpdateLog found - cannot sync" message suggests that either you have disabled the updateLog feature in solrconfig.xml or that you have deleted the tlog directory (or possibly the entire data directory). Hopefully it's the latter, because SolrCloud cannot function properly if the updateLog is disabled. For data integrity reasons, the updateLog is always recommended, whether using SolrCloud or not. Thanks, Shawn
