MatthewCurlerTAC opened a new issue, #41588:
URL: https://github.com/apache/superset/issues/41588

   ### Bug description
   
   I have encountered an intermittent issue where a chart fails to load, 
displaying the error "Data error: Server error" (see screenshot, below). On a 
multi-chart dashboard with will affect only a subset of the charts, even when 
all are using the same dataset, +/- the same filters. Forcing the charts to 
refresh will load the visual as expected.
   
   The issue has impacted multiple dashboards, but intermittently on any given 
dashboard and the charts affected varies.
   
   There do not appear to be any errors in the logs (see attached, below) when 
this error is encountered in the app.
   
   ### Screenshots/recordings
   
   <img width="417" height="265" alt="Image" 
src="https://github.com/user-attachments/assets/77694b15-1376-435d-b50e-fa44a4d11f60";
 />
   
   ### Superset version
   
   6.1.0
   
   ### Python version
   
   I don't know
   
   ### Node version
   
   I don't know
   
   ### Browser
   
   Chrome
   
   ### Additional context
   
   - Superset is running in Docker, using a custom build based on the 6.1.0 tag.
     - The customizations are mainly to include static assets (logos) and 
necessary database drivers
   - The backend database is StarRocks (4.0) using the Python 
`starrocks==1.3.3` package
   - Relevant logs: 
[superset-app-logs.txt](https://github.com/user-attachments/files/29520421/superset-app-logs.txt)
   - Caching is enabled:
   
   ```python
   CACHE_CONFIG: CacheConfig = {
   "CACHE_TYPE": "RedisCache",
   "CACHE_DEFAULT_TIMEOUT": 43200,  # 12 hours
   "CACHE_KEY_PREFIX": "superset_results_",
   "CACHE_REDIS_HOST": REDIS_HOST,
   "CACHE_REDIS_PORT": REDIS_PORT,
   "CACHE_REDIS_DB": 0,
   }
   DATA_CACHE_CONFIG = CACHE_CONFIG
    
   FILTER_STATE_CACHE_CONFIG: CacheConfig = {
   "CACHE_TYPE": "RedisCache",
   "CACHE_DEFAULT_TIMEOUT": 1800,  # 30 minutes
   "CACHE_KEY_PREFIX": "superset_filters_",
   "CACHE_REDIS_HOST": REDIS_HOST,
   "CACHE_REDIS_PORT": REDIS_PORT,
   "CACHE_REDIS_DB": 1,
   }
    
   EXPLORE_FORM_DATA_CACHE_CONFIG: CacheConfig = {
   "CACHE_TYPE": "RedisCache",
   "CACHE_DEFAULT_TIMEOUT": 7200,  # 2 hours
   "CACHE_KEY_PREFIX": "superset_explore_",
   "CACHE_REDIS_HOST": REDIS_HOST,
   "CACHE_REDIS_PORT": REDIS_PORT,
   "CACHE_REDIS_DB": 2,
   }
    
   RESULTS_BACKEND = CacheConfig = {
   "CACHE_TYPE": "RedisCache",
   "CACHE_DEFAULT_TIMEOUT": 1800,  # 30 minutes
   "CACHE_KEY_PREFIX": "superset_results_",
   "CACHE_REDIS_HOST": REDIS_HOST,
   "CACHE_REDIS_PORT": REDIS_PORT,
   "CACHE_REDIS_DB": 4,
   }
   
   DISTRIBUTED_COORDINATION_CONFIG: CacheConfig = {
   "CACHE_TYPE": "RedisCache",
   "CACHE_KEY_PREFIX": "signal_",
   "CACHE_REDIS_URL": f"{REDIS_HOST}:{REDIS_PORT}/7",
   "CACHE_DEFAULT_TIMEOUT": 300,
   }
    
   class CeleryConfig:
   broker_url = f"redis://{REDIS_HOST}:{REDIS_PORT}/3"
   imports = (
   "superset.sql_lab",
   "superset.tasks.scheduler",
   "superset.tasks.thumbnails",
   "superset.tasks.cache",
   )
   result_backend = f"redis://{REDIS_HOST}:{REDIS_PORT}/4"
   worker_prefetch_multiplier = 1
   task_acks_late = False
   beat_schedule = {
   "reports.scheduler": {
   "task": "reports.scheduler",
   "schedule": crontab(minute="*", hour="*"),
   },
   "reports.prune_log": {
   "task": "reports.prune_log",
   "schedule": crontab(minute=10, hour=0),
   },
   }
    
    
   CELERY_CONFIG = CeleryConfig
   ```
   
   
   ### Checklist
   
   - [x] I have searched Superset docs and Slack and didn't find a solution to 
my problem.
   - [x] I have searched the GitHub issue tracker and didn't find a similar bug 
report.
   - [x] I have checked Superset's logs for errors and if I found a relevant 
Python stacktrace, I included it here as text in the "additional context" 
section.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to