40 likes | 171 Views
US LFC Centralization. Plans US has 9 LFCs currently. All T2s and T3s LFC will be consolidated. Target date for the completion is by the end of Sept 2012 Consolidated LFC ust2lfc.usatlas.bnl.gov Multiple head nodes behind F5 Oracle backend. Technical detail.
E N D
US LFC Centralization • Plans • US has 9 LFCs currently. • All T2s and T3s LFC will be consolidated. • Target date for the completion is by the end of Sept 2012 • Consolidated LFC • ust2lfc.usatlas.bnl.gov • Multiple head nodes behind F5 • Oracle backend
Technical detail • All US T2s use LFC with MySQL backend • Data is migrated continuously to BNL MySQL via rubyrep • To reduce the site downtime. Less than one day. • MySQL Dump is used in the case where direct access to the backend MySQL from BNL is not possible. • From BNL’s MySQL, the content is inserted to T2 LFC BNL. • The volume at each LFC is between a few millions and 10 millions replicas.
LFC dump • T2 admin has ability to request the LFC dump via http://www.usatlas.bnl.gov/dq2/lfcdumprequests/index • The request is automatically processed • produce the dump in sqlite format. • The dump is registered to DDM as a dataset and subscribed to a requested site
Site cleanup • There is a script to clean-up/check the site storage. • Compare the LFC dump with the physical files from the storage. • Will be used to cleanup Panda Mover files