[EU Region] Scheduled Metadata Database maintenance

Scheduled Maintenance Report for Treasure Data

Completed

*Maintenance* and system *recovery* have been fully completed.

The scheduled database maintenance is now complete. The downtime was 899 seconds (14 minutes and 59 seconds) in total.

Posted Dec 09, 2020 - 01:15 PST

Verifying

The scheduled database maintenance is complete.

We are monitoring the system closely to ensure all systems successfully complete their *recovery* and return as quickly as possible to full functionality.

Posted Dec 09, 2020 - 01:02 PST

In progress

The scheduled database maintenance window is starting now.

# Impact

During the maintenance and recovery, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

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.
The same will apply to import requests from Browsers (Javascript SDK) and Mobiles (Android, iOS, and Unity SDKs).

- 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.

Posted Dec 09, 2020 - 00:00 PST

Update

In about an hour, from 9:00 AM CEST (0:00 AM PST, 5:00 PM JST), the maintenance window for the PlazmaDB Metadata database will commence.

# Impact

During the maintenance and recovery, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

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.
The same will apply to import requests from Browsers (Javascript SDK) and Mobiles (Android, iOS, and Unity SDKs).

- 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.

# Communication

Beyond this notice, we will provide updates at the start and completion of the operation, and once the verification of the new system is completed. At that time, all systems will have returned to full functionality and this Scheduled Maintenance will be closed.

Posted Dec 08, 2020 - 23:00 PST

Scheduled

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.

# Impact

During the maintenance and recovery, customers may experience the following:

- Streaming, Mobile, and JavaScript/Browser imports delay

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.
The same will apply to import requests from Browsers (Javascript SDK) and Mobiles (Android, iOS, and Unity SDKs).

- 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.

# Communication

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 support@treasuredata.com.

Posted Nov 23, 2020 - 22:45 PST

This scheduled maintenance affected: EU (Web Interface, REST API, Streaming Import REST API, Mobile/Javascript REST API, Data Connector Integrations, Hadoop / Hive Query Engine, Presto Query Engine, Presto JDBC/ODBC Gateway, Workflow, CDP API, Data Access API (beta)).