Notes on staging hgwbeta
- /cluster/home is mounted on hgwbeta, so you can use it
for simple file transfers.
- You can also use the push-request alias or the pushreq utility.
- Contents of goldenPath don't need to be maintained on hgwbeta
(to save disk space).
- When you ask for a large push (> 2 Gb) to hgnfs1, be sure to ask the pushers
to put it on the mirror's 'exclude' list and notify the mirrors that a large file
is on the way. (When you eventually release it to
the RR, ask for it to be taken off the exclude list).
- Make sure the database exists on hgwbeta.
- You can use the command sudo mypush dbname tablename hgwbeta.
For a large number of files, use bigPush.csh
- mypush supports the use of wildcards for tablename (use single quotes).
- mypush will report how many bits were transferred, both data
It is preferable to stage only the contents in extFile/seq that are ready to be pushed.
note: Galt has scripts getSeq.csh and loadSeq.csh that may be useful.
create table seqTransfer (
id int(10) unsigned not null,
acc varchar(24) not null,
size int(10) unsigned not null,
gb_date date not null,
extFile int(10) unsigned not null,
file_offset bigint(20) not null,
file_size int(10) unsigned not null
- Or use hgsqldump db seq --no-data
insert into seqTransfer select * from seq where extFile = value;
- push seqTransfer to hgwbeta
- on hgwbeta, sanity check: select distinct (extFile) from seqTransfer
- on hgwbeta: insert into seq select * from seqTransfer;
- do a similar process for extFile rows
- hgwbeta uses hgcentralbeta, which is on hgwbeta.
- hgwdev uses hgcentraltest, which is on hgwdev.