Forwarding to dev as I seem to have forgotten to set the reply-to.
While we would be interested in improving performance, bh-demo2 is
running the latest release rather than the latest code and this problem
appears only to have manifested itself recently. Admittedly it could be
something that was missed.
This also seems to coincide with some recent work to dist_upgrade hosts.
We have been experiencing similar problems with
issues.apache.org/bloodhound which was running very happily until the
dist_upgrade.
Anyway, I'll keep investigating these problems and hopefully others can
comment further on performance beyond these instances.
Cheers,
Gary
-------- Original Message --------
Subject: RE: Apache Bloodhound demo not accessible
Date: Thu, 31 Jul 2014 17:50:48 +0300
From: Gosh Snobo <[email protected]>
To: 'Gary Martin' <[email protected]>
Hi,
yeah, seems to work now. I have a question though: why the nightly build
demo (https://bh-demo2.apache.org) responds very slow, sometimes almost
unbearable; and latest stable (https://bh-demo1.apache.org) response is
better, but still a bit delayed. Makes me wonder if Bloodhound has
performance issues... Could you please comment on that, if possible?
thanks,
Gosh
------------------------------------------------------------------------
*From:* Gary Martin [mailto:[email protected]]
*Sent:* Thursday, July 31, 2014 4:09 PM
*To:* dev
*Cc:* [email protected]
*Subject:* Re: Apache Bloodhound demo not accessible
Hi,
Seems to have fixed itself but I will look into it further. Thanks for
letting us know.
Cheers,
Gary
On 31 July 2014 12:10, Gosh Snobo <[email protected]
<mailto:[email protected]>> wrote:
Hello,
I'm interested in evaluating Apache Bloodhound. However, the online
demo is not accessible:
https://bh-demo2.apache.org/
The proxy server received an invalid response from an upstream server.
The proxy server could not handle the request/GET /
<https://bh-demo2.apache.org/>/.
Reason:*Error reading from remote server*
any chance on fixing it?
KR,
-=gosh=-
