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  October 2013

QSERV-L October 2013

Subject:

notes from qserv mtg Oct 3

From:

Jacek Becla <[log in to unmask]>

Reply-To:

General discussion for qserv (LSST prototype baseline catalog)

Date:

Mon, 7 Oct 2013 23:24:33 -0700

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (76 lines)

Daniel, AndyH, Douglas, Bill, Serge, Jacek


fdr related
  - need shared scans section from Daniel
  - need wike page with 300-node test descr from Douglas


release planning
  - need tasks (2-4 week worth of work) covering
    now-Aug 2014 (due Oct 9 to Jeff, Jacek coordinating)


discussion about automated testing:
  - use the same data for all tests
  - keep multiple qserv releases (for comparison)
  - run tests before cutting release, then do release,
    then install the release for future comparisons
  - once the core set of queries stabilize,
     it will be easier to compare, now some syntax
     still broken due to new parser
  --> Douglas will implement that


merge engine
  - useful for at least 2 cases:
     a) might be able to avoid subchunks
     b) can be used to subdivide largest tables


logging
  - distinction between local and distributed logging
    is impportant
  - logging is very difficult for large scale distributed
    systems, very few succeeded
  - dedicated discussion within the group, Tue morning 9:15
  - will write proposal about logging and discuss with
    the rest of DM


short term tasks:
* automated testbed
* ingest [Serge]
* logging [Bill likes this topic]
* supported syntax detection
* build system / code organization (scons),
   we are struggling with understanding how
   to use scons, how to structure code, how
   to write clean, proper scons
* packaging (eups?)
    - what about people outside of lsst...
* run time administration, distribution etc,
    - Douglas will write a page on trac
* distributed metadata mgmt
--> Jacek will reorg trac page to reflect that,
     and we will revisit what is left out



[discussion with KT after the meeting:
   - revisit partitioning/subchunking: consider
     tree vs list structure
   - side interface in addition to sql, for things like
     query progress, L3
   - supported syntax detection: pass syntax through
     and auto-validate, don't try to implement code for
     catching each syntax/condition separately]

Jacek

########################################################################
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