In article <[EMAIL PROTECTED]>, Russell E Owen <[EMAIL PROTECTED]> wrote:
I talked to Jacek and here are is one answer: > ** Once one table exists, the easiest way to create another is to ask > the database server to copy it. So...this brings up the question of > initialization. Should the CIS create the first table, e.g. from a > file containing schema, or should a template table be created as part > of setting up the databases initially? The latter is simpler for the > CIS and slightly more efficient (since otherwise each instance of a > CIS needs to first create one table using SQL before copying the > rest), but it's really no big deal. In any case, I have coded the CIS > to work either way -- if a template table is specified, it is used, > else a scheme file must be specified. The plan is for the Catalog Ingest Service (CIS) to have a higher level component that will itself decide such things as: - how many worker processes are best to handle the slices - which slices are handled by which process - perhaps is smart enough to realize that a process is stalled and restart it on a different node (not likely for DC1) That high level component will create the databases (at the beginning of the run) and should probably also create the tables. In the long term (not for DC1), that allows it to apportion the many tables (one per stripe) to the available disks to balance the load. -- Russell _______________________________________________ LSST-data mailing list [email protected] http://www.lsstmail.org/mailman/listinfo/lsst-data
