-
Notifications
You must be signed in to change notification settings - Fork 787
chore(cache): Add minimum threshold for table data disk cache size #18227
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(cache): Add minimum threshold for table data disk cache size #18227
Conversation
Introduce TABLE_DATA_DISK_CACHE_SIZE_THRESHOLD (1024 bytes) to better handle disk cache enabling logic. Any configuration value below this threshold will disable the table data disk cache. This change temporarily addresses an issue with cloud platform deployment where setting the disk cache size to zero prevents the physical volume from being loaded. Additional logging for on-disk cache configuration added to improve diagnostics.
🤖 Smart Auto-retry Analysis
The workflow run has been analyzed for retryable errors using job annotations. 📊 Analysis Summary
⛔️ Retry Status: CANCELLED
🔍 Detailed Job Analysis⛔️ linux / build (x86_64, X64)
🤖 About This AnalysisThis is an automated analysis and retry triggered by the smart retry workflow using job annotations. The system analyzes failure patterns to distinguish between:
Only infrastructure issues are automatically retried to avoid wasting resources on code problems that need manual fixes. |
🤖 Smart Auto-retry Analysis
The workflow run has been analyzed for retryable errors using job annotations. 📊 Analysis Summary
✅ Retry Status: AUTOMATIC RETRY INITIATED
📈 Monitor Progress: View in Actions 🔍 Detailed Job Analysis❌ linux / test_unit
🔄 linux / test_stateless_standalone
🔄 linux / test_stateful_standalone
🔄 linux / sqllogic / standalone_minio (query, http, native)
🤖 About This AnalysisThis is an automated analysis and retry triggered by the smart retry workflow using job annotations. The system analyzes failure patterns to distinguish between:
Only infrastructure issues are automatically retried to avoid wasting resources on code problems that need manual fixes. |
🤖 Smart Auto-retry Analysis
The workflow run has been analyzed for retryable errors using job annotations. 📊 Analysis Summary
✅ Retry Status: AUTOMATIC RETRY INITIATED
📈 Monitor Progress: View in Actions 🔍 Detailed Job Analysis🔄 linux / test_stateless_standalone
🤖 About This AnalysisThis is an automated analysis and retry triggered by the smart retry workflow using job annotations. The system analyzes failure patterns to distinguish between:
Only infrastructure issues are automatically retried to avoid wasting resources on code problems that need manual fixes. |
2 similar comments
🤖 Smart Auto-retry Analysis
The workflow run has been analyzed for retryable errors using job annotations. 📊 Analysis Summary
✅ Retry Status: AUTOMATIC RETRY INITIATED
📈 Monitor Progress: View in Actions 🔍 Detailed Job Analysis🔄 linux / test_stateless_standalone
🤖 About This AnalysisThis is an automated analysis and retry triggered by the smart retry workflow using job annotations. The system analyzes failure patterns to distinguish between:
Only infrastructure issues are automatically retried to avoid wasting resources on code problems that need manual fixes. |
🤖 Smart Auto-retry Analysis
The workflow run has been analyzed for retryable errors using job annotations. 📊 Analysis Summary
✅ Retry Status: AUTOMATIC RETRY INITIATED
📈 Monitor Progress: View in Actions 🔍 Detailed Job Analysis🔄 linux / test_stateless_standalone
🤖 About This AnalysisThis is an automated analysis and retry triggered by the smart retry workflow using job annotations. The system analyzes failure patterns to distinguish between:
Only infrastructure issues are automatically retried to avoid wasting resources on code problems that need manual fixes. |
I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/
Summary
Introduce TABLE_DATA_DISK_CACHE_SIZE_THRESHOLD (1024 bytes) to better handle disk cache enabling logic.
Any configuration value below this threshold will disable the table data disk cache.
This change temporarily addresses an issue with cloud platform deployment where setting the disk cache size to zero prevents the physical volume from being loaded.
Additional logging for on-disk cache configuration added to improve diagnostics.
Tests
Type of change
This change is