Mailinglist Archive: opensuse-buildservice (287 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] Redirector availability
- From: Klaas Freitag <freitag@xxxxxxx>
- Date: Wed, 19 Sep 2007 21:21:52 +0200
- Message-id: <200709192121.52296.freitag@xxxxxxx>
Am Dienstag, 18. September 2007 12:02 schrieb Michael Schroeder:
> On Tue, Sep 18, 2007 at 11:53:14AM +0200, Dr. Peter Poeml wrote:
> > * software.opensuse.org relies on the availability of the internal
> > buildservice backend, for the search and ymp generation. Thus, when
> > the buildservice hangs, the software.opensuse.org search hangs as
> > well. This is unfortunate IMO, but I don't know if there is a way
> > around this.
>
> Just to clarify things: it relies on the availablility of the
> API server (where we had some out of memory trouble) and the
> repository server (rock solid so far). It doesn't rely on the
> scheduler where things aren't so stable due to lots of code changes.
If we would change that to a search_server somehow that combines
search relevant data and functionality from api and repo server
(and src server for build.o.o relevant searches which again
calls the repo server for the work) - wouldn't that make sense?
At least searches for build.o.o have to search in the API database
and the backend AFAIK which is not optimal and the repo server
shouldn't be stressed by searches anyway.
Anything against thinking in that direction? Did I miss something?
Have fun,
Klaas
>
--
Klaas Freitag Architect OPS/IPD
SUSE LINUX Products GmbH - Nuernberg
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
> On Tue, Sep 18, 2007 at 11:53:14AM +0200, Dr. Peter Poeml wrote:
> > * software.opensuse.org relies on the availability of the internal
> > buildservice backend, for the search and ymp generation. Thus, when
> > the buildservice hangs, the software.opensuse.org search hangs as
> > well. This is unfortunate IMO, but I don't know if there is a way
> > around this.
>
> Just to clarify things: it relies on the availablility of the
> API server (where we had some out of memory trouble) and the
> repository server (rock solid so far). It doesn't rely on the
> scheduler where things aren't so stable due to lots of code changes.
If we would change that to a search_server somehow that combines
search relevant data and functionality from api and repo server
(and src server for build.o.o relevant searches which again
calls the repo server for the work) - wouldn't that make sense?
At least searches for build.o.o have to search in the API database
and the backend AFAIK which is not optimal and the repo server
shouldn't be stressed by searches anyway.
Anything against thinking in that direction? Did I miss something?
Have fun,
Klaas
>
--
Klaas Freitag Architect OPS/IPD
SUSE LINUX Products GmbH - Nuernberg
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |