On Wednesday, December 9th from 9 to 10:30 AM CEST (Wednesday, December 9th from 0 AM to 1:30 AM PST, December 9th from 5 to 6:30 PM JST) we will be performing maintenance on the PlazmaDB Metadata database. The maintenance is necessary to improve reliability and maintainability through upgrading the PostgreSQL database engine.
The maintenance operation will be taking around 60 minutes, and the database will become unreachable for the duration of restarting the database, which should last no longer than 20 minutes in total. We expect this to be followed by a recovery period of around 30 minutes during which the system will gradually reach back to full throughput.
During the maintenance and recovery, customers may experience the following:
Streaming import (through td-agent or fluentd) requests will continue to be accepted as usual but the requests will remain queued until after the database maintenance is complete. We expect stream import processing to be further delayed during recovery.
- Jobs execution delay
All jobs (Presto, Hive, Result Export, Data Connector Integrations, Bulk Import, Export, and Partial Delete jobs submitted from Console, API, Workflow or triggered by our system according to the configured schedule) will fail and continue to retry during maintenance. During recovery, we expect jobs to begin processing slowly: within 30 minutes job processing should reach back to full throughput.
- Presto JDBC / ODBC Gateway return errors during downtime
The Presto JDBC / ODBC Gateway will return errors during downtime period.
- Console execution delay
Data Workbench and Audience Studio will show that jobs are running longer due to underlying job execution delay due to failure of the underlying Master Segments, Segments, and Workflows jobs that overlap with the maintenance period. During recovery, we expect processing of Data Workbench and Audience Studio jobs to follow the same recovery pattern as all other jobs (see above).
- Data Access API (beta) return errors during downtime
Data Access API (Plazma Public API) for Spark will return errors during downtime period.
Beyond this notice, we will provide updates approximately 1 hour before the beginning of the maintenance window, at the start and completion of the operation, and once the verification is complete. At that time, all systems will have returned to full functionality and the Scheduled Maintenance will be closed.
If you have any question or concern about this upgrade, please feel free to reach out to our Support team at firstname.lastname@example.org