You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The safepoint calculation is the first step for garbage collection in TiDB, data older than the safepoint could be safely reclaimed. The safepoint must be less than the global minimal start_ts among all the tidb sessions, so a session with long-running transactions may block the advancement of safepoint. For example, if the user starts a transaction but never commits, the safepoint could not be pushed and data reclamation is blocked. To make the diagnosis of such issues easier, consider the following improvements in TiDB:
Record the long-running transaction and session information in the expensive logs. If the safepoint is blocked by some ongoing sessions, the start_ts could be used to locate the blocking session.
Record ongoing transaction duration in the metrics with a certain flushing interval, so the long-running transitions could be viewed directly on the grafana panels.
The text was updated successfully, but these errors were encountered:
Enhancement
The
safepoint
calculation is the first step for garbage collection in TiDB, data older than thesafepoint
could be safely reclaimed. Thesafepoint
must be less than the global minimalstart_ts
among all the tidb sessions, so a session with long-running transactions may block the advancement ofsafepoint
. For example, if the user starts a transaction but never commits, thesafepoint
could not be pushed and data reclamation is blocked. To make the diagnosis of such issues easier, consider the following improvements in TiDB:safepoint
is blocked by some ongoing sessions, thestart_ts
could be used to locate the blocking session.The text was updated successfully, but these errors were encountered: