[
https://issues.apache.org/jira/browse/SOLR-7666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14935086#comment-14935086
]
Upayavira commented on SOLR-7666:
---------------------------------
[~arafalov] I've tried my own system, and I'm not getting the healthcheck
message, and logging is working for me. I triggered a logging event with this
URL:
http://localhost:8983/solr/images/select?q=\[
Could you try that (change the core name of course) and see whether logging
works, or whether you get any exceptions/stacktraces?
I did a bit more digging into "ping" support. I didn't realise the possibility
of configuring a file that will take a node/core out of a load balancer, but
the nice thing is, when you add the relevant stuff to solrconfig.xml, the UI
behaves as it should, even though it was never tested :-)
Please try with the latest trunk, or lucene_5x branch, and let me know if you
see any more healthcheck issues.
Thanks!
> Umbrella ticket for Angular JS post-5.2.1 issues
> ------------------------------------------------
>
> Key: SOLR-7666
> URL: https://issues.apache.org/jira/browse/SOLR-7666
> Project: Solr
> Issue Type: New Feature
> Components: UI
> Affects Versions: 5.3, Trunk
> Reporter: Erick Erickson
> Assignee: Upayavira
> Attachments: SOLR-7666-part2.patch, SOLR-7666-part2.patch,
> SOLR-7666.patch, admin-ui-7666.zip
>
>
> As of Solr 5.2.1, there's a new admin UI available that has been written
> almost entirely by Upayavira (thanks!) over the last several months. It's
> written in Angular JS with an eye towards enhancement/maintainability. The
> default UI is still the old version, but you can access the new version by
> going to http://<sever:port>/solr/index.html. There are a couple of fixes
> between 5.2.0 and 5.2.1, so please use either a fresh 5x checkout, trunk, or
> 5.2.1....
> The expectation is that in Solr 5.3, the new code will become the default
> with the old UI deprecated and eventually removed.
> So it would be a great help if volunteers could give the new UI a spin. It
> should look much the same as the current one at the start, but evolve into
> something much more interesting and more cloud-friendly. Of course all the
> new UI code will always be available on trunk/6.0 too, and the up-to-date
> code will always be on both the trunk and 5x branches.
> Please provide feedback on the user's (or dev) lists about anything you find
> that doesn't work, or enhancements you'd like to see (or, even better,
> contribute). If you raise a JIRA, please link it to this one so I can keep
> track of what needs to be committed. If linking JIRAs is a mystery just add a
> comment to this JIRA referencing the new JIRA and we can take care of it.
> Please do _not_ attach patches to this JIRA, it'll be much easier to keep
> track of everything if the patches are attached to sub-JIRAs.
> And a big thanks to Upayavira for this work!
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
