lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark Miller (JIRA)" <>
Subject [jira] [Commented] (SOLR-3648) /browse returns this stack trace to the browser HTTP ERROR 500
Date Fri, 20 Jul 2012 20:56:35 GMT


Mark Miller commented on SOLR-3648:

There are a variety of extras that may not work with SolrCloud - I don't consider any of them
blockers though. Initially, I would only expect core stuff to work well until others start
digging into other components. I have never looked at how the UIMA update processor plays
with SolrCloud as an example. Unless a lot of people start asking about something like that,
it's just not high on my priority list.

Of course, a lot of this could be done by anybody.

I look at this the same as some search components not yet supporting distrib. Some things
won't work with SolrCloud to begin with as well. I've focused my attention on the core features.

Currently, anything anywhere that tries to get the local fs directory will fail when in SolrCloud
mode. In the cases that you can accomplish the same thing using zookeeper, another code path
can be added. I've done this for a couple other things. In some cases it might not be so easy

That exception is telling you, in cloud mode, this feature is not currently support - perhaps
we should tweak it to be more explicit about that.

Since I'm not familiar with browse or what it tries to do internally, it's not high on my
personal list, which is quite long.
> /browse returns this stack trace to the browser HTTP ERROR 500
> --------------------------------------------------------------
>                 Key: SOLR-3648
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SearchComponents - other
>    Affects Versions: 4.0-ALPHA
>         Environment: RHEL 5.4, SolrCloud
>            Reporter: Nick Cotton
>            Priority: Blocker
>              Labels: patch
>             Fix For: 4.0
> When run in a SolrCloud configuration the Velocity searchHandler responds to a /browse
request with an HTTP error 500 and a stack trace indicating
> ZkSolrResourceLoader does not support getConfigDir() 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message