ZkSync Outage: What Happened and How it was Fixed

04/02/2023 00:26 • Crypto & Markets • 69 views

On April 2, according to official news, the zkSync team announced the reason for the outage on Twitter. Blocking stopped due to a failure in the block queue database. However, the server API was not affected. Transactions continue to be added to the memory pool, and the query service is normal. Although all components have comprehensive monitoring, logging, and alerts, no alerts were triggered due to the API’s normal operation. The entire team was offline when the accident occurred. The fix was implemented in 5 minutes. To address similar issues, zkSync assigns a special role to database monitoring agents, enabling them to connect to the database and continuously collect metrics. At the same time, the team introduced an alert mechanism that alerts when the database monitoring agent fails or cannot establish a connection to the database. In addition, if the situation escalates significantly, the team on standby will be notified immediately through multiple channels. But the only long-term solution is decentralization.

ZkSync: Database failures lead to downtime, and decentralization is the only long-term solution

Introduction

On April 2, the zkSync team announced an outage on Twitter. The reason for the outage was a failure in the block queue database, which resulted in the blocking being stopped. This article will dive deeper into what happened and how the team fixed the issue.

The Outage

According to official news, the zkSync team discovered the outage on April 2. The outage was caused by a failure in the block queue database. However, the server API was not affected. Transactions continued to be added to the memory pool, and the query service remained normal.
Although all components have comprehensive monitoring, logging, and alerts, no alerts were triggered due to the API’s normal operation. The entire team was offline when the accident occurred.

How it was fixed

The fix was implemented within 5 minutes. To address similar issues in the future, zkSync assigned a special role to database monitoring agents. This enabled them to connect to the database and continuously collect metrics. Additionally, the team introduced an alert mechanism that alerts when the database monitoring agent fails or cannot establish a connection to the database.
If the situation escalates significantly, the team on standby will be notified immediately through multiple channels. However, the only long-term solution is decentralization.

Why Decentralization is Key

Decentralization is key to ensuring that the entire system does not fail due to centralized points of failure. By distributing the responsibility and control of the system, any failures can be contained and fixed more quickly. Additionally, decentralization makes it more difficult for bad actors to disrupt the system.

Conclusion

The zkSync team was swift in addressing the outage that occurred due to a failure in the block queue database. They introduced measures to prevent similar issues from occurring in the future, including assigning a special role to database monitoring agents and introducing an alert mechanism. However, the only long-term solution is decentralization.

FAQs

**Q1. What is zkSync?**
Ans: zkSync is a scaling solution for Ethereum that enables fast and low-cost transactions.
**Q2. Why is decentralization important?**
Ans: Decentralization is important because it ensures that any failures are contained and fixed more quickly. Additionally, it makes it more difficult for bad actors to disrupt the system.
**Q3. How long did it take to fix the outage?**
Ans: The outage was fixed within 5 minutes.

This article and pictures are from the Internet and do not represent qiAiAi's position. If you infringe, please contact us to delete:https://www.qiaiai.com/crypto/13205.html

It is strongly recommended that you study, review, analyze and verify the content independently, use the relevant data and content carefully, and bear all risks arising therefrom.