LISTSERV mailing list manager LISTSERV 16.5

Help for QSERV-L Archives


QSERV-L Archives

QSERV-L Archives


QSERV-L@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

QSERV-L Home

QSERV-L Home

QSERV-L  September 2015

QSERV-L September 2015

Subject:

Re: Czar Failover et. al.

From:

Jacek Becla <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Fri, 4 Sep 2015 13:28:16 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (47 lines)

Andy

I am not sure I see the connection between assigning query
to a different czar and your comment "if we explode queries
into 1000's of pieces and then try to handle reassembly in
a single place"

I do like the idea of assigning query to a different char.
It'd help not only with balancing load between czars, but
also with things like gracefully taking down a czar.

Let's have this discussion on the qserv mailing list, there
are others that will surely be interested in this topic.

I'm happy to turn that into story/stories/epics. Let's wait
few more days to see where this email discussion (and qserv
hangout discussion?) will take us, then we can readjust the
plan wrt to czar failover.

Thanks
Jacek


On 09/04/2015 12:36 PM, Andrew Hanushevsky wrote:
> Hi Jacek,
>
> Perhaps we need a new story. My last comment on failover pretty much
> said that I don't think it's worth all of the effort from a practical
> stand-point. However, there is a related item that (sort of) involves
> failover. I'm thinking how we could load balance czar's after the fact.
> The idea is that it might be interesting if we explore being able to
> reassign queries to differt czars after the query is started. This would
> give us flexibility on how we distribue the reassembly load. As it
> stands now, the system probably won't scale very well if we explode
> queries into 1000's of pieces and then try to handle reassembly in a
> single place.
>
> Let me know if this thought process is something we should explore.
>
> Andy

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the QSERV-L list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=QSERV-L&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

March 2018
February 2018
January 2018
December 2017
August 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use