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

   ### Bug description
   
   Getting the following every minute on the worker node:
   
   ```
   [2024-07-26 09:46:17,568: ERROR/MainProcess] Received unregistered task of 
type 'reports.scheduler'.
   The message has been ignored and discarded.
   
   Did you remember to import the module containing this task?
   Or maybe you're using relative imports?
   
   Please see
   https://docs.celeryq.dev/en/latest/internals/protocol.html
   for more information.
   
   The full contents of the message body was:
   b'[[], {}, {"callbacks": null, "errbacks": null, "chain": null, "chord": 
null}]' (77b)
   
   The full contents of the message headers:
   {'lang': 'py', 'task': 'reports.scheduler', 'id': 
'2ef01d9c-99ce-47e5-92b5-aeccc773aa66', 'shadow': None, 'eta': None, 'expires': 
None, 'group': None, 'group_index': None, 'retries': 0, 'timelimit': [None, 
None], 'root_id': '2ef01d9c-99ce-47e5-92b5-aeccc773aa66', 'parent_id': None, 
'argsrepr': '()', 'kwargsrepr': '{}', 'origin': 
'gen41@superset-celerybeat-xxxxxx', 'ignore_result': False, 
'replaced_task_nesting': 0, 'stamped_headers': None, 'stamps': {}}
   
   The delivery info for this task is:
   {'exchange': '', 'routing_key': 'celery'}
   Traceback (most recent call last):
     File 
"/usr/local/lib/python3.10/site-packages/celery/worker/consumer/consumer.py", 
line 659, in on_task_received
       strategy = strategies[type_]
   KeyError: 'reports.scheduler'
   ```
   
   And no reports run at all.
   
   I don't have this issue in 4.0.2 with the same config
   
   
   ### How to reproduce the bug
   
   Installed 4.1.0rc1-py310 on k8s
   
   ```
   class CeleryConfig:
         broker_url = 'rediss://%s:%s/%s?ssl_cert_reqs=CERT_NONE' % 
(REDIS_HOST, REDIS_PORT, REDIS_CELERY_DB)
         imports = ('superset.sql_lab', "superset.tasks", 
"superset.tasks.thumbnails", )
         result_backend = 'rediss://%s:%s/%s?ssl_cert_reqs=CERT_NONE' % 
(REDIS_HOST, REDIS_PORT, REDIS_CELERY_DB)
         worker_log_level = "DEBUG"
         worker_prefetch_multiplier = 4
         task_acks_late = True
         task_annotations = {
             "sql_lab.get_sql_results": {"rate_limit": "100/s"},
             "email_reports.send": {
                 "rate_limit": "1/s",
                 "time_limit": int(timedelta(seconds=600).total_seconds()),
                 "soft_time_limit": int(timedelta(seconds=600).total_seconds()),
                 "ignore_result": True,
             },
         }
         beat_schedule = {
             "reports.scheduler": {
                 "task": "reports.scheduler",
                 "schedule": 59.95,
             },
             "reports.prune_log": {
                 "task": "reports.prune_log",
                 "schedule": crontab(minute=0, hour=0),
             },
             'cache-warmup-hourly': {
                   'task': 'cache-warmup',
                   'schedule': crontab(minute=26, hour='*'),  # @hourly
                   'kwargs': {
                       'strategy_name': 'top_n_dashboards',
                       'top_n': 20,
                       'since': '7 days ago',
                   },
               },
         }
   
       CELERY_CONFIG = CeleryConfig
   ```
   
   ### Screenshots/recordings
   
   _No response_
   
   ### Superset version
   
   master / latest-dev
   
   ### Python version
   
   3.10
   
   ### Node version
   
   Not applicable
   
   ### Browser
   
   Not applicable
   
   ### Additional context
   
   _No response_
   
   ### 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: notifications-unsubscr...@superset.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscr...@superset.apache.org
For additional commands, e-mail: notifications-h...@superset.apache.org

Reply via email to