Experiment Support CERN IT Department CH-1211 Geneva 23 Switzerland t DBES L. Betev, A. Grigoras, C. Grigoras, P. Saiz, S. Schreiner AliEn Extreme Job Broker

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 210 Nov 2011 Pablo Saiz ALICE offline week Two tasks: –Tells CE how many JobAgents to submit –Gives user jobs to JobAgents –Using job priorities Using Classads matchmaking Pull mode –Waits for requests Critical service –Without it, user jobs would wait in the queue Multiple instances, in several hosts –Using DB to solve concurrency problems AliEn Job Broker

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 310 Nov 2011 Pablo Saiz ALICE offline week xrootd Job execution Job Manager JOB TASKQUEUE Job Broker CE MonALISA xrootd Site A JOB MonALISA xrootd Site B MonALISA Site C File catalogue LFN GUID Meta data JOB CE JA

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 410 Nov 2011 Pablo Saiz ALICE offline week Current Job Broker concerns Increased number of jobs –More users, more analysis, more resources… Load on server(s) –We could deploy more instances. –No problems with database performance Understand why jobs stay in WAITING

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 510 Nov 2011 Pablo Saiz ALICE offline week Let’s go back to splitting… Splitting per SE –Per combination of SE –Users can specify max number of files Although usually jobs have even less input files Other splitting algorithms are trivial –‘production’  similar jdl in all subjobs –‘file’  one subjob per file –‘directory’  one subjob per directory –‘user defined’  as user specifies

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 610 Nov 2011 Pablo Saiz ALICE offline week Current situation Works nicely if one replica per file Job Manager JOB A bit more complex with 3 SE and 2 replicas Job Manager JOB And a lot more with 50 SE and 3 replicas Job Manager JOB

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 710 Nov 2011 Pablo Saiz ALICE offline week What if...? Split jobs without specifying input data per subjob Decide files to be analyzed in the last moment –Based on location, and files already analyzed

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 810 Nov 2011 Pablo Saiz ALICE offline week Example Site ASite BSite C File 1 File 2 File 3 File 4 File 5 Current schema Submit 4 jobs: File1 File 4 File2File3File 5 Broker per file Submit 3 empty subjobs File1, 2,4,5 When a job starts, analyze as much as possible File 3 If nothing left, just exit

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 910 Nov 2011 Pablo Saiz ALICE offline week Even more options ‘Each subjob with at least 5 files’ –And read them remotely ‘Analyze only 70 out of 100 files’ –And stop once the number has been reached ‘Stop the analysis after 3 hours when 90% of files have been processed’ Ideas from: Jan Fiete Grosse-Oetringhaus

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 1010 Nov 2011 Pablo Saiz ALICE offline week Broker per file Benefits: –Less subjobs –Easier to achieve max number entries –Can define min number (remote reading) –Can reduce the tail of execution Challenges: –Keep track of files analyzed –Increase complexity of Broker –Still to be implemented

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 1110 Nov 2011 Pablo Saiz ALICE offline week Load on Job Broker Increase with v2-19: –Security: SSL connections

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 1210 Nov 2011 Pablo Saiz ALICE offline week Old Classad Matchmaking PrioJobsJDL [executable=“aliroot”; user=‘alidaq’; inputdata=; …; Requirements= TTL>9000 and other.SE=‘ALICE::FZK::SE’ ] 975 [executable=“aliroot”; user=‘psaiz’, inputdata= …; Requirements= TTL>300 and ( other.SE=‘ALICE::Prague::SE’ or other.SE=‘ALICE::Torino::SE’) ] 9520 [executable=“aliroot”; user=‘blabla’; inputdata = …; Requirements= TTL>300 and other.SE=‘ALICE::CERN::SE’ ] … [executable=“aliroot”; user=‘aliprod’; Requirements=TTL>80000] Match all entries, starting with highest priority [ Uname = " server"; CE = "ALICE::CERN::aliendb5"; CloseSE = { "ALICE::CERN::Castor2", "ALICE::CERN::SE", … }; Version = "v "; Type = "machine"; Price = E+00; Host = "aliendb5d"; WNHost = "aliendb5.cern.ch"; LocalDiskSpace = ; Platform = "Linux-x86_64"; TTL = 43200; Packages = { …} ; Requirements = ( other.Type == "Job" ) ] JOB AGENT JDL

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 1310 Nov 2011 Pablo Saiz ALICE offline week Current Classad Matchmaking Match all entries with that SE, starting with highest priority PrioJobsJDLSE [executable=“aliroot”; user=‘alidaq’; packages=; …; Requirements= TTL>9000 and other.SE=‘ALICE::FZK::SE’ ] FZK 975 [executable=“aliroot”; user=‘psaiz’, packages=; …; Requirements= TTL>300 and ( other.SE=‘ALICE::Prague::SE’ or other.SE=‘ALICE::Torino::SE’) ] Torino, Prague 9520 [executable=“aliroot”; user=‘blabla’; packages=; …; Requirements= TTL>300 and other.SE=‘ALICE::CERN::SE’ ] CERN … [executable=“aliroot”; user=‘aliprod’; Requirements=TTL>80000]

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 1410 Nov 2011 Pablo Saiz ALICE offline week And in v2-20 Let the database do most of matchmaking –Extract most common fields from the JDL: TTL, CE, SE, user, partition, size, packages.. –First match should do it –Less flexibility in requirements… PrioJobsJDLSEUser CE …Partition [executable=“aliroot”; …]FZKalidaqFZK 975 [executable=“aliroot”; … ]Torino, Prague psaizTorino, Prague 9520 [executable=“aliroot”; … ]CERNblablaCERN … [executable=“aliroot”; … ]aliprod

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 1510 Nov 2011 Pablo Saiz ALICE offline week Other changes in v2-20 ‘Resubmit’ uses same jobid CE submits JA even if packages not installed Atomic transaction for job assignment

CERN IT Department CH-1211 Geneva 23 Switzerland t ES 1610 Nov 2011 Pablo Saiz ALICE offline week Summary AliEn Job Broker –Decides where jobs get executed –Pull model, classads and priorities In next version of AliEn –Broker per file to be analyzed Less subjobs More input dat per subjob More options (min. files, max waiting time) –Simplified classad matching –Atomic job assignment transaction To be deployed in January