celery task scheduled but not executed at ETA
I have my celery configured as following:
# create context tasks in celery
celery = Celery(
__name__,
# redis
backend=app.config['CELERY_RESULT_BACKEND'],
broker=app.config['CELERY_BROKER_URL'],
include=['app.celery_tasks.tasks']
)
celery.conf.timezone = 'US/Pacific'
celery.conf.broker_transport_options = {'visibility_timeout': 3600*24}
celery.conf.task_routes = {
'tasks.periodic': {
'queue': 'periodic',
'routing_key': 'tasks.periodic'
},
'tasks.generate_report': {
'queue': 'report',
'routing_key': 'tasks.generate_report'
}
}
Then I'm using this helper method to get eta for all my report tasks
def get_eta_time(time_d=8):
tz = timezone('US/Pacific')
ct = datetime.now(tz=tz)
eta = ct + timedelta(hours=time_d)
return eta
The thing I'm encountering is I can see the tasks are scheduled using the celery control but they are not executed when the eta arrives. However, when I tried to restart my celery workers, these tasks got picked up immediately. Is there anything I missed in my celery config?
My tasks are triggered as following:
eta = get_eta_time()
generate_report.apply_async(args=(log_location, repetition_count+1), queue='report', eta=eta)
My periodical queue works as expected, but my report queue is not making any sense to me.
python celery celery-task
edited Nov 28 '18 at 1:48
davidism
64.9k12172188
asked Nov 27 '18 at 21:59
KhalilKhalil
14
add a comment |
I have my celery configured as following:
# create context tasks in celery
celery = Celery(
__name__,
# redis
backend=app.config['CELERY_RESULT_BACKEND'],
broker=app.config['CELERY_BROKER_URL'],
include=['app.celery_tasks.tasks']
)
celery.conf.timezone = 'US/Pacific'
celery.conf.broker_transport_options = {'visibility_timeout': 3600*24}
celery.conf.task_routes = {
'tasks.periodic': {
'queue': 'periodic',
'routing_key': 'tasks.periodic'
},
'tasks.generate_report': {
'queue': 'report',
'routing_key': 'tasks.generate_report'
}
}
Then I'm using this helper method to get eta for all my report tasks
def get_eta_time(time_d=8):
tz = timezone('US/Pacific')
ct = datetime.now(tz=tz)
eta = ct + timedelta(hours=time_d)
return eta
The thing I'm encountering is I can see the tasks are scheduled using the celery control but they are not executed when the eta arrives. However, when I tried to restart my celery workers, these tasks got picked up immediately. Is there anything I missed in my celery config?
My tasks are triggered as following:
eta = get_eta_time()
generate_report.apply_async(args=(log_location, repetition_count+1), queue='report', eta=eta)
My periodical queue works as expected, but my report queue is not making any sense to me.
python celery celery-task
edited Nov 28 '18 at 1:48
davidism
64.9k12172188
asked Nov 27 '18 at 21:59
KhalilKhalil
14
What version of celery are you using? There are some issues with using a non-UTC timezone in older versions of celery.
– 2ps
Nov 28 '18 at 19:37
yeah, I looked at those posts too, but I'm using 4.2.1 the latest. It's like the workers only fetch tasks when they first started, but no more fetching after the first time. And the weirdest part is it was working fine 2 weeks ago, and I didn't make any significant changes after that.
– Khalil
Nov 28 '18 at 19:44
add a comment |
I have my celery configured as following:
# create context tasks in celery
celery = Celery(
__name__,
# redis
backend=app.config['CELERY_RESULT_BACKEND'],
broker=app.config['CELERY_BROKER_URL'],
include=['app.celery_tasks.tasks']
)
celery.conf.timezone = 'US/Pacific'
celery.conf.broker_transport_options = {'visibility_timeout': 3600*24}
celery.conf.task_routes = {
'tasks.periodic': {
'queue': 'periodic',
'routing_key': 'tasks.periodic'
},
'tasks.generate_report': {
'queue': 'report',
'routing_key': 'tasks.generate_report'
}
}
Then I'm using this helper method to get eta for all my report tasks
def get_eta_time(time_d=8):
tz = timezone('US/Pacific')
ct = datetime.now(tz=tz)
eta = ct + timedelta(hours=time_d)
return eta
The thing I'm encountering is I can see the tasks are scheduled using the celery control but they are not executed when the eta arrives. However, when I tried to restart my celery workers, these tasks got picked up immediately. Is there anything I missed in my celery config?
My tasks are triggered as following:
eta = get_eta_time()
generate_report.apply_async(args=(log_location, repetition_count+1), queue='report', eta=eta)
My periodical queue works as expected, but my report queue is not making any sense to me.
python celery celery-task
edited Nov 28 '18 at 1:48
davidism
64.9k12172188
asked Nov 27 '18 at 21:59
KhalilKhalil
14
I have my celery configured as following:
# create context tasks in celery
celery = Celery(
__name__,
# redis
backend=app.config['CELERY_RESULT_BACKEND'],
broker=app.config['CELERY_BROKER_URL'],
include=['app.celery_tasks.tasks']
)
celery.conf.timezone = 'US/Pacific'
celery.conf.broker_transport_options = {'visibility_timeout': 3600*24}
celery.conf.task_routes = {
'tasks.periodic': {
'queue': 'periodic',
'routing_key': 'tasks.periodic'
},
'tasks.generate_report': {
'queue': 'report',
'routing_key': 'tasks.generate_report'
}
}
Then I'm using this helper method to get eta for all my report tasks
def get_eta_time(time_d=8):
tz = timezone('US/Pacific')
ct = datetime.now(tz=tz)
eta = ct + timedelta(hours=time_d)
return eta
The thing I'm encountering is I can see the tasks are scheduled using the celery control but they are not executed when the eta arrives. However, when I tried to restart my celery workers, these tasks got picked up immediately. Is there anything I missed in my celery config?
My tasks are triggered as following:
eta = get_eta_time()
generate_report.apply_async(args=(log_location, repetition_count+1), queue='report', eta=eta)
My periodical queue works as expected, but my report queue is not making any sense to me.
python celery celery-task
python celery celery-task
edited Nov 28 '18 at 1:48
davidism
64.9k12172188
asked Nov 27 '18 at 21:59
KhalilKhalil
14
edited Nov 28 '18 at 1:48
davidism
64.9k12172188
asked Nov 27 '18 at 21:59
KhalilKhalil
14
edited Nov 28 '18 at 1:48
davidism
64.9k12172188
edited Nov 28 '18 at 1:48
davidism
64.9k12172188
edited Nov 28 '18 at 1:48
davidism
64.9k12172188
64.9k12172188
asked Nov 27 '18 at 21:59
KhalilKhalil
14
asked Nov 27 '18 at 21:59
KhalilKhalil
14
asked Nov 27 '18 at 21:59
KhalilKhalil
14
14
What version of celery are you using? There are some issues with using a non-UTC timezone in older versions of celery.
– 2ps
Nov 28 '18 at 19:37
yeah, I looked at those posts too, but I'm using 4.2.1 the latest. It's like the workers only fetch tasks when they first started, but no more fetching after the first time. And the weirdest part is it was working fine 2 weeks ago, and I didn't make any significant changes after that.
– Khalil
Nov 28 '18 at 19:44
add a comment |
What version of celery are you using? There are some issues with using a non-UTC timezone in older versions of celery.
– 2ps
Nov 28 '18 at 19:37
yeah, I looked at those posts too, but I'm using 4.2.1 the latest. It's like the workers only fetch tasks when they first started, but no more fetching after the first time. And the weirdest part is it was working fine 2 weeks ago, and I didn't make any significant changes after that.
– Khalil
Nov 28 '18 at 19:44
What version of celery are you using? There are some issues with using a non-UTC timezone in older versions of celery.
– 2ps
Nov 28 '18 at 19:37
What version of celery are you using? There are some issues with using a non-UTC timezone in older versions of celery.
– 2ps
Nov 28 '18 at 19:37
yeah, I looked at those posts too, but I'm using 4.2.1 the latest. It's like the workers only fetch tasks when they first started, but no more fetching after the first time. And the weirdest part is it was working fine 2 weeks ago, and I didn't make any significant changes after that.
– Khalil
Nov 28 '18 at 19:44
yeah, I looked at those posts too, but I'm using 4.2.1 the latest. It's like the workers only fetch tasks when they first started, but no more fetching after the first time. And the weirdest part is it was working fine 2 weeks ago, and I didn't make any significant changes after that.
– Khalil
Nov 28 '18 at 19:44
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53508861%2fcelery-task-scheduled-but-not-executed-at-eta%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53508861%2fcelery-task-scheduled-but-not-executed-at-eta%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
What version of celery are you using? There are some issues with using a non-UTC timezone in older versions of celery.
– 2ps
Nov 28 '18 at 19:37
yeah, I looked at those posts too, but I'm using 4.2.1 the latest. It's like the workers only fetch tasks when they first started, but no more fetching after the first time. And the weirdest part is it was working fine 2 weeks ago, and I didn't make any significant changes after that.
– Khalil
Nov 28 '18 at 19:44