Q: What has changed from version 1.1.0 to 1.2.0
A: Below is a list of changes:
  • The performance is 5 to 10 percent faster than the previous release (1.1.0).
  • Tables
  • cntlmonAPI:

    • database web page
      • add Engineering and science runs description to the databases
    • cntlmon server
      • Handled situation if there are no DSOs in system ( e.g. /lal not mounted )
      • New function to gather statistics of beowulf loads to support cmonClient load summary report.
      • Defaults archived log retention from 6 months to 1 year.
      • Fixed error of "No ymin" for API time graph data when there is only one category selected and there are no jobs fitting this category.
      • New function to gather thread usage data for graphing threads vs time.
    • Utilities
      • log monitor (logscan )
        • report errors by logging to cntlmon's logs instead of stderr.
      • database web page builder (db2utils) -
        • added Engineering and science runs dates to the database page
        • fixed schema page to report correctly columns that require non-nulls
      • log filtering (bgcntlmon)
        • migrated procs out from genericAPI into log filter program
      • database creation
        • include deletion of triggers when creating new database
      • cmonClient
        • added new page cache view to show frame times (PR1729)
        • added new graph under System resources to show thread usage vs time.
        • added new page Load Summary under MPI to show beowulf node usage vs time
        • added X-axis and Y-axis totals to histograms
        • migrated histograms to be invoked from their time graphs instead of independent of them; support rebin of histograms
        • added ldas command and DSO to the printed output of graphs with such filters
        • added subtotals of each category for API time metrics graph.
  • diskcacheAPI:

    • A distribution of just the pieces needed for creating a diskcache library has been created. It is intended for use in data discovery tools.
    • Added function to gather diskcache file-system usage data for each mount-point which gets the number of directories and number of files under that mount point that matches a specified ifo and type.
    • Added function to gather diskcache interval data. It gets a list of intervals within a specific start and stop time matching a specified ifo and type.
    • Added functions to set/get the frame file extension.
  • eventmonAPI:

    • created new proc to set insertion rate
    • Allowed update of insertion rate via cmonClient resource page.
    • Sent email if the update value is incorrect.
    • Unregister thread and thread variable to prevent assertion errors detected during putStandAlone exception test.
  • frameAPI:

    • LDAS can now specify users to have create directory priveleges so systems do not need to be "seeded" with output directories for the createRDS commands. Below is an example of how to use this variable in the LDASframe.rsc file:
        ;## desc=list of users who may write RDS files anywhere
        set ::USERS_WHO_CAN_CREATE_RDS_DIRS [ list mlei createrdstest anderson bjohnson_ldas gmendell igor nobody ]
        
    • Additionally, users can be restricted to creating directories to certain directories by means of the ::USER_CAN_WRITE_RDS_TO_DIRS variable also in LDASframe.rsc file. For example
      
          ;## desc=ARRAY of users who may write RDS files to specified dirs
          set ::USER_CAN_WRITE_RDS_TO_DIRS(nobody) [ list /only/here /only/there ]
        
      Allows the user nobody to create subdirectories only under /only/here and /only/there.
  • genericAPI:

    • Mail handling by LDAS can now be done two different ways.
      • Method 1 (Recommended) Defining ::USE_SENDMAIL_AS_MTA to be 1, and setting ::PATH_TO_SENDMAIL to the correct path will cause LDAS to use sendmail as the MTA. Below is an example configuration for ldas-dev.ligo.caltech.edu.
        
            ;## desc=this should be set to the fully qualified name of your mailhost!!
            set ::LDAS_MAIL_RELAY_FQDN acrux.ligo.caltech.edu
        
            ;## desc=set to '1' to use 'sendmail -oi -t' to deliver mail
            set ::USE_SENDMAIL_AS_MTA 1
        
            ;## desc=path to sendmail executable
            set ::PATH_TO_SENDMAIL /usr/lib/sendmail
            
      • Method 2 (Not Recommended) Defining ::USE_SENDMAIL_AS_MTA to be 0, and setting ::LDAS_MAIL_RELAY_FQDN to be the fully qualified domain name of a mailserver that will relay mail for the LDAS gateway will cause LDAS to use it's own MTA, which is much less fault tolerant than sendmail.
  • metadataAPI:

    • Updated job time out from 50 secs to 100 secs to allow sleepy dataRecv threads to wakeup in time to complete job. Increase bgLoop for waking dataRecv threads from 10 secs to 60 secs. PR 2435
  • mpiAPI:

    • A much faster startup/shutdown is now possible when user ldas has sudo priveleges for the search users. The file /etc/sudoers needs to have the following entries:
      
        User_Alias  LDAS_PGM = ldas
        Cmnd_Alias  PKILL = /usr/bin/pkill
        LDAS_PGM    ALL= NOPASSWD: PKILL
        
      This file must be edited by a person with system administrative priveleges. For ldas systems, please contact ldas sysadmins; all others please contact your local system administrator. To make use of the sudo priveleges, you will need to modify the LDASmpi.rsc file simularly to the example given below.
      
        ;## desc=lam processes can be killed en-masse if user ldas has sudo
        set ::USER_LDAS_HAS_SUDO 1
      
        ;## desc=globbing style sudo kill command for this platform.
        set ::MPI_SUDO_KILL_COMMAND "sudo pkill -9 -u \[ join \$::MPIUSERS , \]"
        
  • Closed Problem Reports




Back to LDAS FAQ