QA/Browser Technologies/Services/Releases/SyncServer 06292011

Information

• Train: Sync Server 06-29-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

Resolved/Verified Bugs

• bug 666805 - deploy python sync
• bug 667588 - Monitoring for nginx 499 timeouts
• bug 667570 - serve 503s when nginx has a 499
• bug 667726 - bad query for getting the timestamps
• Ops Bug 667721
• bug 667731 - trying myconnpy
• bug 667598 - memcached size bad resync
• bug 667846 - queries are getting locked on high load

Opened Bugs/Issues

• bug 668394 - First sync failed on stage
• bug 668443 - The collection timestamp gets updated on empty DELETEs
• bug 668564 - Getting Quota values of 0 on Stage
• bug 668573 - alter database schema to prevent NULL payload sizes
• bug 668572 - Inspect production data to see if we have payload_size NULL
• bug 667074 - Ensure that the python sync storage code handles NULL payload_size

Notes

• This is the second attempt to deploy the first big Python Sync Server to Production.