My _guess_ is that you're getting a cached page somehow and never getting to Solr at all when you don't see the new core. What happens if you look at the admin UI from another machine? Or perhaps a different browser?
If you tail the Solr log when you are looking you should see the request when you try to see the new core, if you don't see a request come through then it's a caching issue... Or perhaps try issuing a core admin STATUS command? http://solr:port/solr/admin/cores?action=STATUS Best, Erick On Wed, Jul 8, 2015 at 6:14 AM, Jens Brandt <bra...@docoloc.de> wrote: > Hi, > > there was a problem with zookeeper and IPv6 that could be solved by using > -Djava.net.preferIPv4Stack=true. Now, the core is correctly created, but I am > wondering why I cannot see the core on the web interface, neither on the core > admin screen nor in the Core Selector field. Only after restarting solr the > core shows up on the web interface. > > Best Regards, > Jens > > >> Am 07.07.2015 um 12:49 schrieb Jens Brandt <bra...@docoloc.de>: >> >> Hi Erick, >> >> thanks for your reply. >> >> after creating the new collection via CollectionAPI I can see in the solr >> log files that the core was created: >> >> Solr index directory '/var/lib/solr/gagel_shard1_replica1/data/index' >> doesn't exist. Creating new index... >> >> However, when calling >> >> curl "http://solrtest:8080/solr/gagel/query?q=*:*"; >> >> I get an HTTP 404 error: >> >> <html> >> <head> >> <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> >> <title>Error 404 Not Found</title> >> </head> >> <body><h2>HTTP ERROR 404</h2> >> <p>Problem accessing /solr/tubs/query. Reason: >> <pre> Not Found</pre></p><hr><i><small>Powered by >> Jetty://</small></i><hr/> >> </body> >> </html> >> >> >> >> >>> Am 06.07.2015 um 19:51 schrieb Erick Erickson <erickerick...@gmail.com>: >>> >>> bq: However, the named core is created but not loaded in solr. >>> >>> I'm not quite sure what that means, what is the symptom you see? >>> Because this should be fine. I've sometimes been fooled by looking >>> at the core admin UI screen and not reloading it. What happens >>> if you try querying your new collection directly right after you create >>> it? e.g. >>> >>> http://blah blah/solr/gagel/query?q=*:* >>> >>> You should get back a valid packet. Admittedly with 0 hits, but if the >>> core were truly not loaded you'd get an error. >>> >>> And please, please, please do NOT use the core admin screen to try >>> to add cores in SolrCloud mode. It's possible to use, but you must >>> know _exactly_ what parameters to set or Bad Things Happen. >>> Continue to use the collections API, it's safer. >>> >>> Best, >>> Erick >>> >>> >>> On Mon, Jul 6, 2015 at 8:54 AM, Jens Brandt <bra...@docoloc.de> wrote: >>>> Hi, >>>> >>>> I am trying to setup SolrCloud with external zookeeper. Solr 5.2.1 is >>>> running on host solrtest at port 8080 and zookeeper already contains a >>>> config with the name customerSolr. When I create a new collection using >>>> the CollectionAPI by calling the following url: >>>> >>>> http://solrtest:8080/solr/admin/collections?action=CREATE&numShards=1&collection.configName=customerSolr&name=gagel"; >>>> >>>> I get a positive response and the core name "gagel_shard1_replica1" is >>>> returned. However, the named core is created but not loaded in solr. When >>>> I trie to manually add the core by using the Core Admin webinterface I get >>>> the error that the core already exists. After a restart of solr the core >>>> is loaded correctly. >>>> >>>> Can anyone please advise if I am doing something wrong or maybe this is an >>>> issue in solr 5.2.1? >>>> >>>> Best Regards, >>>> Jens >> >
