my apologies for the lack of clarity our internal name for the project to upgrade solr from 4.0 to 4.10.2 is "helios" and so we named our test folder "heliosearch". I was not even aware of the github project Heliosearch, and nothing we are doing is related to it.
to simplify things for this post, we simplified things so that we have one solr instance but two cores; coreX contains the collection1 files/folders as per the downloaded solr 4.10.2 package, while coreA uses the same collection1 files/folders but with schema.xml and solrconfig.xml changes to meet our needs so file and foldername-wise, here is what we did: 1. C:\SOLR\solr-4.10.2.zip\solr-4.10.2\example renamed to C:\SOLR\helios-4.10.2\Master 2. renamed example\solr\collection1 to example\solr\coreX; no files modified here 3. copied example\solr\coreX to example\solr\coreA 4. modified the coreA schema to match our current production schema; ie our field names, etc 5. modified the coreA solrconfig.xml to meet our needs (see below) here are the solrconfig.xml changes we made to coreA 1. <directoryFactory name="DirectoryFactory" class="${solr.directoryFactory:solr.StandardDirectoryFactory}"> 2. <mergeFactor>4</mergeFactor> 3. <reopenReaders>false</reopenReaders> 4. <infoStream>false</infoStream> 5. commented out autoCommit section 6. commented out autoSoftCommit section 7. commented out the <cache name="perSegFilter"...> section 8. <maxWarmingSearchers>4</maxWarmingSearchers> 9. <requestParsers enableRemoteStreaming="true" multipartUploadLimitInKB="2048000" /> 10. <requestHandler name="/select" class="solr.SearchHandler"> contains <arr name="last-components"><str>geocluster</str></arr> 11. commented out these sections: <requestHandler name="/browse" class="solr.SearchHandler"> <requestHandler name="/spell" class="solr.SearchHandler" startup="lazy"> <requestHandler name="/suggest" class="solr.SearchHandler" startup="lazy"> <searchComponent name="suggest" class="solr.SuggestComponent"> <searchComponent name="tvComponent" class="solr.TermVectorComponent"/> <requestHandler name="/tvrh" class="solr.SearchHandler" startup="lazy"> <searchComponent name="clustering" ... <requestHandler name="/clustering"... <searchComponent name="elevator" class="solr.QueryElevationComponent" > <requestHandler name="/elevate" class="solr.SearchHandler" startup="lazy"> <queryResponseWriter name="xslt" class="solr.XSLTResponseWriter"> here are the schema.xml changes we made to our copy of the downloaded solr 4.10.2 package (aside from replacing the example fields provided in the downloaded solr 4.10.2): 1. <schema name="Helios" version="1.5"> 2. removed the example fields provided in the downloaded solr 4.10.2 3. delete various types we dont use in our current schemas 4. added fieldtypes that are in our current solr 4.0 instances 5. added various fieldtypes that are in our current solr 4.0 instances 6. readded the "text" field as apparently required: <field name="text" type="text_general" indexed="true" stored="false" multiValued="true"/> also note that we are using java "1.7.0_67" and jetty-8.1.10.v20130312 all in all, I dont see anything that we have done that would keep the cores from being discovered. hope that helps. -- View this message in context: http://lucene.472066.n3.nabble.com/Solr-4-10-2-Found-core-but-I-get-No-cores-available-in-dashboard-page-tp4173602p4173831.html Sent from the Solr - User mailing list archive at Nabble.com.