Changes between Initial Version and Version 1 of tier-one-meeting-20170926


Ignore:
Timestamp:
09/26/17 15:17:53 (4 years ago)
Author:
paul
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • tier-one-meeting-20170926

    v1 v1  
     1[[TOC(depth=0)]] 
     2= dCache Tier I meeting September 26th, 2017 = 
     3[part of a [wiki:developers-meetings series of meetings]] 
     4 
     5== Present == 
     6 
     7dCache.org(Paul), IN2P3(), Sara(), Triumf(), BNL(), NDGF(Ulf), PIC(), KIT(Samuel), Fermi(), CERN() 
     8 
     9= Agenda = 
     10 
     11(see box on the other side) 
     12 
     13= Site reports = 
     14 
     15== NDGF == 
     16 
     17Currently going quite well. 
     18 
     19Finally got the Danish pool online. 
     20 
     21Started -- checksum of all the files -- 2.5x10^6 files => 1 week to complete checksum. 
     22 
     23When starting up -- the pool doesn't check whether the file is acceptable permissions on start-up.  This is only discovered when trying to read the file (e.g. checksum ) 
     24 
     25Ulf to open a ticket. 
     26 
     27== KIT == 
     28 
     29Everything is running fine 
     30 
     31Upgraded ATLAS instance -- everything work, but update took a long time. 
     32 
     33=== Database locks === 
     34 
     35Liquibase seems to lock the entire database -- could it lock just the table it is operating on? 
     36 
     37This would allow upgrades to happen concurrently (e.g., pinmanager, srm, spacemanager, ..) 
     38 
     39Paul suggested placing the different services in different databases (possibly keeping them within the same DBMS system).  This is now the default configuration, although many sites have the old deployment with all non-chimera databases in a single database called "srm". 
     40 
     41=== GPFS logical manager issue === 
     42 
     43RT ticket 9217. 
     44 
     45After some discussion, the desire is to have a dCache pool start so that data stored on the pool can be migrated off onto another pool. 
     46 
     47I.e., have a pool start in "emergency mode" where it does not attempt to modify any data and allows only pool-to-pool transfers. 
     48 
     49=== Pool startup === 
     50 
     51RT ticket 9214. 
     52 
     53The fast switch from disabled to read-only is appreciated; however, the full start-up still takes a long time. 
     54 
     55The concern is that, if they need to restart all pools then ATLAS cannot write data until the first pool has completed its start-up. 
     56 
     57After some discussion, it seems that the pool is CPU bound, using a single thread. 
     58 
     59= Support tickets for discussion = 
     60 
     61[Items are added here automagically] 
     62 
     63= DTNM = 
     64 
     65Same time, next week.