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
When continuous profiling is enabled, the tidbngmonitoring service begins to crash loop after a particular time. With 10GB of storage, it enters a crash loop within approximately 3 days; this extends to about 9 days when storage is increased to 40GB. Given the 3-day retention period, I did not anticipate storage to be the issue. The pod exits with exit code 255, and the logs are insufficient to identify the problem.
Used version: docker.io/pingcap/ng-monitoring:v8.0.0
The text was updated successfully, but these errors were encountered:
When continuous profiling is enabled, the tidbngmonitoring service begins to crash loop after a particular time. With 10GB of storage, it enters a crash loop within approximately 3 days; this extends to about 9 days when storage is increased to 40GB. Given the 3-day retention period, I did not anticipate storage to be the issue. The pod exits with exit code 255, and the logs are insufficient to identify the problem.
Used version: docker.io/pingcap/ng-monitoring:v8.0.0
The text was updated successfully, but these errors were encountered: