So after adding some docs to the index (and committing) with those two nodes active, do segment files magically appear?
My _guess_ is that there's something radially wrong with you set up the collection. Did you by any chance use the core admin API to create the cores? That can lead to "interesting" results of you don't get everything just right. For instance, if you point the data dir for all three nodes at the same directory... What does your clusterstate.json file look like? Best, Erick On Thu, Feb 12, 2015 at 8:30 AM, Zisis Tachtsidis <zist...@runbox.com> wrote: > I'm using SolrCloud 4.10.3 and the current setup is simple using 3 nodes with > 1 shard. After a rolling restart of the Solr cluster I've ended up with 2 > failing nodes reporting the following > > org.apache.solr.servlet.SolrDispatchFilter > null:org.apache.solr.common.SolrException: SolrCore 'core' is not available > due to init failure: Error opening new searcher > Caused by: org.apache.solr.common.SolrException: Error opening new searcher > at org.apache.solr.core.SolrCore.openNewSearcher(SolrCore.java:1574) > at org.apache.solr.core.SolrCore.getSearcher(SolrCore.java:1686) > at org.apache.solr.core.SolrCore.<init>(SolrCore.java:853) > ... 8 more > Caused by: java.nio.file.NoSuchFileException: /path/to/index/segments_1 > at > sun.nio.fs.UnixException.translateToIOException(UnixException.java:86) > at > sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:102) > at > sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:107) > at > sun.nio.fs.UnixFileSystemProvider.newFileChannel(UnixFileSystemProvider.java:177) > at java.nio.channels.FileChannel.open(FileChannel.java:287) > at java.nio.channels.FileChannel.open(FileChannel.java:334) > at > org.apache.lucene.store.MMapDirectory.openInput(MMapDirectory.java:196) > at > org.apache.lucene.store.Directory.openChecksumInput(Directory.java:113) > at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:341) > at > org.apache.lucene.index.SegmentInfos$1.doBody(SegmentInfos.java:454) > at > org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:906) > at > org.apache.lucene.index.SegmentInfos$FindSegmentsFile.run(SegmentInfos.java:752) > at org.apache.lucene.index.SegmentInfos.read(SegmentInfos.java:450) > at org.apache.lucene.index.IndexWriter.<init>(IndexWriter.java:792) > at > org.apache.solr.update.SolrIndexWriter.<init>(SolrIndexWriter.java:77) > at > org.apache.solr.update.SolrIndexWriter.create(SolrIndexWriter.java:64) > at > org.apache.solr.update.DefaultSolrCoreState.createMainIndexWriter(DefaultSolrCoreState.java:279) > at > org.apache.solr.update.DefaultSolrCoreState.getIndexWriter(DefaultSolrCoreState.java:111) > at org.apache.solr.core.SolrCore.openNewSearcher(SolrCore.java:1537) > ... 10 more > > Checking the index directory of each node I found out that only > *segments.gen* was inside. What I could not determine is how I ended up with > this single file. Looking at the logs I could not find anything related. The > 3rd node had its index intact. > Has anyone else encountered something similar? > > > > -- > View this message in context: > http://lucene.472066.n3.nabble.com/Index-directory-containing-only-segments-gen-tp4186045.html > Sent from the Solr - User mailing list archive at Nabble.com.
