# Details on the July 29 and August 1 downtime

> Asana had downtime twice in the past week, 2 hours on July 29 and 50 minutes on August 1. We are continuing investigation, but want to let you know what we understand so far, we have made and are making to prevent a recurrence in the short-term.

Source: https://asana.com/inside-asana/july-29-august-1-downtime

## Details on the July 29 and August 1 downtime

Asana had downtime twice in the past week, 2 hours on July 29 and 50 minutes on August 1. We are continuing investigation, but want to let you know what we understand so far, and what changes we have made and are making to prevent a recurrence in the short-term.

Both of these incidents were caused by high database contention. This contention occurred on a database that is shared across all teams and workspaces (e.g. user authentication methods, like OAuth applications). We’ve been working on breaking up our monolithic application into services, and one of our goals with that project is to replace this database with a more scalable distributed data store. That work is ongoing, and currently we do writes to this database for objects that are shared across teams and workspaces.

In the short term, we’ve reduced the write frequency for a property that appears to have triggered the start of both events (the OAuth application last accessed time, which was by far the most frequently updated property). We’ve also fixed some bugs and modified database configuration to reduce deadlocks/contention, and updated our emergency response procedures to improve how we recover from such outages in the future.

We are committed to Asana being a service that you can consistently rely on, and this week did not meet our standards. We’ll provide a follow-up post with more information about what happened as soon as the investigation is complete, along with what we plan on doing to address this class of problem in the future (both near- and long-term).

- [擴展 LunaDb，我們內部的宣告式資料載入系統](/zh-tw/resources/scaling-lunadb)

工程

#### 平台工程師

在 Asana，我們建立了一個名為 LunaDb 的資料載入系統，作為我們 Web 應用程式的骨幹。 儘管名字如此，但它並非資料庫。 相反地，它是一個類似 GraphQL 的系統，用於以宣告式方式擷取資料，基本上是一種載入最新版本資料和所有未來更新的方法。我們最初在 2015 年推出 LunaDb，作為對後端基礎架構的徹底重寫¹。 此新系統的核心元件是同步 ...

- [Asana 如何讓我成為更有效的工程經理](/zh-tw/inside-asana/asana-makes-me-effective-engineering-manager)

工程

#### 資料基礎結構工程經理

As an engineering manager, I need to keep track of so many things. I have my own personal to-dos that I need to prioritize, making time for focused work while also handling incomi ...

- [擴展我們的無效管線：第 1 部分](/zh-tw/inside-asana/scaling-invalidation-pipeline-part-1)

工程

#### 平台工程師

At Asana, our invalidation pipeline is a key part of implementing near-realtime reactivity in the webapp. Reactivity is how each-and-every Asana tab keeps up-to-date with the lat ...

- [Details on the July 29 and August 1 downtime](/zh-tw/inside-asana/july-29-august-1-downtime)

工程

Asana had downtime twice in the past week, 2 hours on July 29 and 50 minutes on August 1. We are continuing investigation, but want to let you know what we understand so far, and ...

- [工程](/inside-asana/engineering-spotlight)