Presto performance improvement release
Scheduled Maintenance Report for Treasure Data
After the release of the Presto performance improvements, we have been monitoring the system for 2 hours and observed no anomaly.

We will now mark this scheduled release as closed but we are committed to continue closely monitoring for the next 3 days.
Posted Jul 06, 2020 - 21:15 PDT
The scheduled Presto performance improvement release 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 Jul 06, 2020 - 19:46 PDT
Scheduled maintenance is still in progress. We will provide updates as necessary.
Posted Jul 06, 2020 - 19:20 PDT
In progress
The scheduled Presto performance improvement release is starting now.

The release should have no impact on running queries, which will transparently be transferred to the new Presto query engine version.
Posted Jul 06, 2020 - 19:16 PDT
In about an hour, from 19:15 to 20:15 PDT (11:15 to 12:15 JST/KST) we will release a hotfix for the Presto query engine.

The release rolls forward the changes that were introduced on May 7th to improve the query performance degradation experienced by queries in specific scenarios.

The May 7th release was rolled back on May 22nd because it had a bug causing sporadic write inconsistencies in CREATE TABLE AS, INSERT INTO, and DELETE FROM queries. This new version, based on the May 7th release, contains an additional fix for the write inconsistency issue.

Both performance degradation and write inconsistency issues are described in detail in the postmortem at

The release should have no impact on running queries, which will transparently be transferred to the new Presto query engine version.

As communicated in the last postmortem, due to the Presto write inconsistency having affected the data integrity of the platform, we have taken the following additional precautions:

* Remediation
We removed the code responsible for the aggressive write optimization that caused the write inconsistency bug.

* Verification
We have reproduced the write inconsistency issue and we built a reliable set of tests to confirm the fix is effective.

* Detection
We implemented additional application logic to detect eventual race conditions (e.g. throw an exception, alert about the anomaly, etc...) when writing into our Plazma storage. Should a race condition even occur (not expected), it will raise an exception forcing the query to error out and an alert to be sent to our staff. Upon receiving an alert, our staff will investigate the situation and when warranted, reach out to the customer to recommend data recovery.

* Monitoring
Our Presto monitoring and alerting was improved. Our team will follow an on-call duty rotation to monitor the health of the system post release for an extended amount of time (96 hours or 3 days) and catch any anomalies.

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

If you have any question or concern about this maintenance, please feel free to reach out to our Support team at
Posted Jul 06, 2020 - 18:05 PDT
This scheduled maintenance affected: Tokyo (Presto Query Engine), Korea (Presto Query Engine), and US (Presto Query Engine).