Changes between Version 1 and Version 2 of developers-meeting-20141210


Ignore:
Timestamp:
12/10/14 16:00:44 (5 years ago)
Author:
karsten
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • developers-meeting-20141210

    v1 v2  
    44 
    55= Participants = 
     6Al, Dmitry, Gerd, Tigran, Karsten, Christian 
    67 
    78= Agenda = 
     
    1718No questions until we get through everyone :) 
    1819 
     20Karsten: Smallfiles for DPHep and Docukenmtnation 
     21 
     22Christian: Tickets!, pcells -> testing, Patches 
     23 
     24Al: Decoupled Alarms from other sercvice 
     25 
     26Dmitry: Metawork 
     27 
     28Gerd: Helping KIT upgrade 
     29 
     30Tigran: Debugging NFS problems with CMS instance 
     31 
    1932= Special topics = 
     33 
     34== KIT upgrade == 
     35Gerd:  
     36   Successfully upgraded, Spacemanager problems, because of stuff (e.g., indices) in tables 
     37   Duplicated records, null values - no idea why. 
     38   Currently restoring 2.6 dump 
     39   Made a patch to solve those issues for other sites 
     40    
     41   Issue with duplicated records remaining. 
     42 
     43== CMS NFS == 
     44Tigran: 
     45   50% of worker nodes use NFS4.1 now 
     46   From last thursday, maybe caused by network problems, problems started to occur, 
     47   pool were online but not serving data, patch committed, other patches running but  
     48   not yet in repo. 
     49   More problems with network caused new problems -> NFS4.1 offline 
     50   -> will setup another NFS door for other use cases so users and worker nodes don't interfere.  
     51   -> split reads and writes and metadata operations 
     52 
     53   -> open question: why are we falling back to proxy IO 
     54 
     55Dmitry:  
     56   - we have a case of one direcotry where ls takes some seconds and ls -l takes about 2h. 
     57   - Also GridFTP transfers looks to kill performance and push up IO wait 
    2058 
    2159= Trunk activity = 
     
    2361Progress with new features... 
    2462 
     63- xrootd4j update requires update of plugins. 
     64 
     65- ipv6 patch 7571 
     66 
    2567= Issues from [FIXME: Add link to yesterday's Tier-1 meeting] = 
     68 
     69PIC: will upgrade to 2.10 on monday 
     70KIT: no issues with dCache, will upgrade to 2.11 soon. 
    2671 
    2772= Plans for patch-releases = 
     
    2974Should we make a new patch release? 
    3075 
     76- 
     77 
    3178= Outstanding Documentation = 
    3279 
    3380= Outstanding RT Tickets = 
    3481 
    35 http://rt.dcache.org/Ticket/Display.html?id=8557 - SRM default port - should we change srmclient? 
    36 http://rt.dcache.org/Ticket/Display.html?id=8561 - xrootd movers 
    37 http://rt.dcache.org/Ticket/Display.html?id=8508 8509 8499 - ipv6 
    38 http://rt.dcache.org/Ticket/Display.html?id=8561 - xrootd movers 
    39 http://rt.dcache.org/Ticket/Display.html?id=8556 - advice on configuring hot pool replication 
    40  
    41  
    42  
     82http://rt.dcache.org/Ticket/Display.html?id=8557 - SRM default port - should we change srmclient? -> won't ix 
     83http://rt.dcache.org/Ticket/Display.html?id=8561 - xrootd movers -> we could somehow work around this, but it is not critical. 
     84http://rt.dcache.org/Ticket/Display.html?id=8508 8509 8499 - ipv6 -> Gerd has a patch, what does it fix?  
     85http://rt.dcache.org/Ticket/Display.html?id=8556 - advice on configuring hot pool replication -> trial and error 
     86                                                   Better to spread data in the first place using migration/balance 
     87                                                   0.7 might be a good number (Tigran) 
     888400 -> is documented 
    4389 
    4490= Review of RB requests = 
     91 
     92There are some WebAdmin patches 7484, 7508 + 7503, please review again 
     93Al, Gerd: billing patch 
    4594 
    4695= New, noteworthy and other business =