QA/Browser Technologies/Services/Releases/SyncServer 06272011

• Information
  • Train: Sync Server 06-27-2011

• Links
  • Bugs/Issues: see Bugzilla
  • Test Plans
    • https://wiki.mozilla.org/QA/Sync/Test_Plan#Servers
    • https://wiki.mozilla.org/QA/Sync/Test_Plan/Test_Level_Summaries#Smoketests_plus_2
  • Stage Documentation: https://intranet.mozilla.org/QA/Server_Weekly_Trains_Staging
  • Stage Environment
    • https://intranet.mozilla.org/Services/Ops/StageCluster
    • https://intranet.mozilla.org/QA/Mozilla_Services_Environment

• Deployment Ticket/Maintenance Window Info
  • Bug 666805 - deploy python sync
  • https://intranet.mozilla.org/Services/Ops/ChangeWindow_20110627

• Resolved/Verified Bugs
  • Bug 667588 - Monitoring for nginx 499 timeouts
  • Bug 667570 - serve 503s when nginx has a 499

• Opened Bugs/Issues
  • Bug 667726 - bad query for getting the timestamps
  • Bug 667721 - (bug is locked)
  • Bug 667731 - trying myconnpy
  • Bug 667598 - memcached size bad resync
  • Bug 667846 - queries are getting locked on high load

• Notes
  • This train failed in Stage and was rolled back.

• • Split "services" log into two parts: Part 1 was for S-C Branch Release QA testing, Part 2 is Python Sync Server deployment.
    • Part 1 is in "#services 5.colloquyTranscript"
    • Part 2 is in "#services 6.colloquyTranscript"
    • Issues
      • PHX Load
      • PHX MySQL too many connections (MySQL rejecting its connections)
      • DB API Errors
      • OPs: we need a better async mysql query solution
      • OPs: conclusion of python failure: database driver (client side) issues
    • For more details, see this email: "Partial Sync outage during PySync roll-out -- 27 June 2011"