koustavnest commented on issue #25944:
URL: https://github.com/apache/superset/issues/25944#issuecomment-1813856365
I have used broker_url as Redis Server and set result_backend as PostgreSQL
Database.
In PostgreSQL, timezone is set as default my current timezone.
It was worked for me Apache Superset 2.1.0 with downgrade the package as
pip install Flask==2.1.3
pip install kombu==5.2.4
pip install MarkupSafe==2.1.2
pip install rich==13.3.5
pip install trio-websocket==0.10.2
pip install typing_extensions==4.6.2
pip install urllib3==2.0.2
pip install tzdata==2023.3
But, in Apache Superset celery server 5.3.4 dose not support kombu >=5.3.3.
In Superset_config.py , I have added this line to celeryconfig
from celery.schedules import crontab
REDIS_HOST = "localhost"
REDIS_PORT = "7000"
import ssl
class CeleryConfig(object):
imports = (
'superset.sql_lab',
'superset.tasks',
)
broker_url = "redis://localhost:7000/0"
result_backend = 'db+postgresql://postgres:XXXX@localhost/XXXX'
task_annotations = {
'sql_lab.get_sql_results': {
'rate_limit': '100/s',
},
'email_reports.send': {
'rate_limit': '1/s',
'time_limit': 120,
'soft_time_limit': 150,
'ignore_result': True,
},
}
task_protocol = 1
beat_schedule = {
"email_reports.schedule_hourly": {
"task": "email_reports.schedule_hourly",
"schedule": crontab(minute=1, hour="*"),
},
"reports.scheduler": {
"task": "reports.scheduler",
"schedule": crontab(minute="*", hour="*"),
},
"reports.prune_log": {
"task": "reports.prune_log",
"schedule": crontab(minute=0, hour=0),
},
}
CELERY_CONFIG = CeleryConfig
It is working for me if I schedule Report as per UTC Time and change
Postgres DB timezone as UTC.
Are you use Celery Server and Redis as broker URL and PostgreSQL as back end
?
Can you please help me where should I change to get Schedule Email in GMT
time
--
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]
