Yes very similar. I had hard coded /solr but it was these locations. I'll
update to use the provided patch and reverify on Monday.
On Saturday, April 7, 2012, Stefan Matheis
wrote:
> Hey Jamie
>
> On Saturday, April 7, 2012 at 2:45 AM, Jamie Johnson wrote:
>> Thanks Ryan. So to be clear this is a
Hey Jamie
On Saturday, April 7, 2012 at 2:45 AM, Jamie Johnson wrote:
> Thanks Ryan. So to be clear this is a bug then? I went into the
> cloud.js and changed the url used to access this information so that
> it would work, wasn't sure if it was kosher or not.
Yes, it's a bug. My only installati
Thanks Ryan. So to be clear this is a bug then? I went into the
cloud.js and changed the url used to access this information so that
it would work, wasn't sure if it was kosher or not.
On 4/6/12, Ryan McKinley wrote:
> There have been a bunch of changes getting the zookeeper info and UI
> looki
There have been a bunch of changes getting the zookeeper info and UI
looking good. The info moved from being on the core to using a
servlet at the root level.
Note, it is not a request handler anymore, so the wt=XXX has no
effect. It is always JSON
ryan
On Fri, Apr 6, 2012 at 7:01 AM, Jamie J
I looked at our old system and indeed it used to make a call to
/solr/zookeeper not /solr/corename/zookeeper. I am making a change
locally so I can run with this but is this a bug or did I much
something up with my configuration?
On Fri, Apr 6, 2012 at 9:33 AM, Jamie Johnson wrote:
> I just down
I just downloaded the latest snapshot and fired it up to take a look
around and I'm getting the following error when looking at the Cloud
view.
Loading of undefined failed with HTTP-Status 404
The request I see going out is as follows
http://localhost:8501/solr/slice1_shard1/zookeeper?wt=json
t