1 / 9

STAR MySQL DB Implementation Overview

STAR MySQL DB Implementation Overview. STAR Database Strategy Production DB Cases Server Deployments Client Access and Server Administration. STAR Database Strategy. STAR-Objy replaced w/ light-wt MySQL -1999 Concerns with MySQL Data transfer bottleneck – single server socket

landrya
Télécharger la présentation

STAR MySQL DB Implementation Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. STAR MySQL DB Implementation Overview • STAR Database Strategy • Production DB Cases • Server Deployments • Client Access and Server Administration R. Jeff Porter, PPDG Site Review

  2. STAR Database Strategy • STAR-Objy replaced w/ light-wt MySQL -1999 • Concerns with MySQL • Data transfer bottleneck – single server socket • Single server storage limitations • Strategy: budget DB data & develop multiple server capabilities • Optimize data sizes at sub-system implementation • Deploy task-specific servers where applicable • Data replication w/ MySQL mirror servers for load balancing & wide-area deployment R. Jeff Porter, PPDG Site Review

  3. STAR Database Strategy Employed  Online & Offline • Online: Experimental Conditions, RunLog, EvtTag • Fine-grained indexing (~109/year), ~100GB/year • Real-time system critical to small #-users during data-taking • Several task-specific servers not for general use • Offline: Geometry, Calibrations, RunInfo • Moderate-grained indexing (~107/year), 10-20GB/year • Managed updates (per production set) , 1000s of users • 1 repository w/ many mirrors deployed where needed • STAR’s quick ramp-up use of MySQL w/ heavy reliance on mirrorsUse MySQL’s native replication R. Jeff Porter, PPDG Site Review

  4. Production DB Use Cases R. Jeff Porter, PPDG Site Review

  5. Online Server Online Server Online Server Online Server Updating Offline Master Repository Offline Master Repository Calibration & DB Writer processes Raw data R. Jeff Porter, PPDG Site Review

  6. Offline mirror Offline mirror Offline mirror RCRS mirror Current Status of Offline Server Deployment Offline Master Repository RCF Reco Farm General mirror RCF Analysis Farm BNL Firewall PDSF mirror WSU mirror Brazil mirror World wide access PDSF Farm WSU Farm SVT code dev R. Jeff Porter, PPDG Site Review

  7. Server Selection from Client • Servers are selected via one or more XML configuration files which include • A default server for all unspecified DB • One or more servers mapped to specified DBs • Client codes select the XML files to use via • Default afs-resident dbServers.xml pointing to our general-use server • Environment variable $STDB_SERVERS R. Jeff Porter, PPDG Site Review

  8. Mirror Server Setup & Administration • Mirrors are set up by hand • tar/scp databases to mirror machine • Edit mirror-specific config files & run scripts to configure startup • Start mirror server and slave process • Monitoring mirror • Run scripts to test mirror is functioning • Run scripts to compare global counts between mirror and master R. Jeff Porter, PPDG Site Review

  9. Comments • MySQL replication has been very robust • Number of mirror servers will steadily increase … for next year, • 2-4 more at BNL • 2-4 more at PDSF • New site-specific mirrors (MPI, DUBNA,…) R. Jeff Porter, PPDG Site Review

More Related