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

Should be able to specify seconds in RecurringJobScheduler #167

Open
sgrassie opened this Issue Jul 17, 2014 · 18 comments

Comments

@sgrassie

sgrassie commented Jul 17, 2014

The RecurringJobScheduler should be able to set a job to reoccur every X seconds.

There is support for this in NCrontab see #7, although a build has not yet been released.

I think it would involve making a change here, such that CrontabSchedule.Parse takes a second options argument, where you specify that you want to recognise six-part crontab expressions.

@Caldas

This comment has been minimized.

Show comment
Hide comment
@Caldas

Caldas Aug 6, 2014

This would be great 👍

Caldas commented Aug 6, 2014

This would be great 👍

@odinserj

This comment has been minimized.

Show comment
Hide comment
@odinserj

odinserj Aug 18, 2014

Member

Unfortunately, that change is proposed to be included in 2.0 version only (it hasn't released yet). I asked @atifaziz about his plans to release it here, so let's wait for the answer.

In case of unresolved conversation, we can fork the project and make the NCrontab2 package, but let's wait first.

Member

odinserj commented Aug 18, 2014

Unfortunately, that change is proposed to be included in 2.0 version only (it hasn't released yet). I asked @atifaziz about his plans to release it here, so let's wait for the answer.

In case of unresolved conversation, we can fork the project and make the NCrontab2 package, but let's wait first.

@odinserj

This comment has been minimized.

Show comment
Hide comment
@odinserj

odinserj Aug 19, 2014

Member

NCrontab 2.0 released! Now we need to prepare Hangfire's RecurringJobScheduler, because it wakes up only every minute now. And there should be some caching mechanism, because it is terrible to query job storage every one second.

Member

odinserj commented Aug 19, 2014

NCrontab 2.0 released! Now we need to prepare Hangfire's RecurringJobScheduler, because it wakes up only every minute now. And there should be some caching mechanism, because it is terrible to query job storage every one second.

@sgrassie

This comment has been minimized.

Show comment
Hide comment
@sgrassie

sgrassie Aug 19, 2014

Good that it has been released. And I agree, it would be terrible to query every second. I do need to schedule some jobs to run every 20 seconds, or every 45 seconds.

sgrassie commented Aug 19, 2014

Good that it has been released. And I agree, it would be terrible to query every second. I do need to schedule some jobs to run every 20 seconds, or every 45 seconds.

@odinserj

This comment has been minimized.

Show comment
Hide comment
@odinserj

odinserj Aug 19, 2014

Member

Just curious - what kind of background processing do you want to perform every 20 seconds?

Member

odinserj commented Aug 19, 2014

Just curious - what kind of background processing do you want to perform every 20 seconds?

@sgrassie

This comment has been minimized.

Show comment
Hide comment
@sgrassie

sgrassie Aug 19, 2014

Emailed you separately about that ㊙️

sgrassie commented Aug 19, 2014

Emailed you separately about that ㊙️

@odinserj odinserj added this to the 1.1.0 milestone Aug 19, 2014

@Caldas

This comment has been minimized.

Show comment
Hide comment
@Caldas

Caldas Aug 20, 2014

In my case in will be summarizing data from a ElasticCache and sending it to a Splunk System

Caldas commented Aug 20, 2014

In my case in will be summarizing data from a ElasticCache and sending it to a Splunk System

@odinserj odinserj modified the milestones: 1.2.0, 1.1.0 Sep 3, 2014

@odinserj odinserj modified the milestones: 1.2.0, 1.2.1 Nov 17, 2014

@bbakkebo

This comment has been minimized.

Show comment
Hide comment
@bbakkebo

bbakkebo May 6, 2015

Hi, I am currently testing 1.40, but I cannot see that it was updated. Hangfire works great, but I have one job that needs to run everything 30 seconds..Is there a workaround to this?
Thanks in advance. 👍

bbakkebo commented May 6, 2015

Hi, I am currently testing 1.40, but I cannot see that it was updated. Hangfire works great, but I have one job that needs to run everything 30 seconds..Is there a workaround to this?
Thanks in advance. 👍

@reggieboyYEAH

This comment has been minimized.

Show comment
Hide comment
@reggieboyYEAH

reggieboyYEAH Apr 20, 2016

Hi @bahram-hodjaev i tested this and this does not work,
this will only run the job once.

any update on this? i have a job that needs to run every 30 seconds.

Thanks in advance :)

reggieboyYEAH commented Apr 20, 2016

Hi @bahram-hodjaev i tested this and this does not work,
this will only run the job once.

any update on this? i have a job that needs to run every 30 seconds.

Thanks in advance :)

@LordMike

This comment has been minimized.

Show comment
Hide comment
@LordMike

LordMike Jul 28, 2016

Is there an update on this?
I'll probably try the Enqueue/Schedule trick, but if Hangfire internally only works in minutes, then that's not gonna work.. :/

LordMike commented Jul 28, 2016

Is there an update on this?
I'll probably try the Enqueue/Schedule trick, but if Hangfire internally only works in minutes, then that's not gonna work.. :/

@alisherdavronov

This comment has been minimized.

Show comment
Hide comment
@alisherdavronov

alisherdavronov Nov 23, 2016

how about enqueue delayed jobs in every minute? if 5 second granularity needed there will be 30 jobs every minute

alisherdavronov commented Nov 23, 2016

how about enqueue delayed jobs in every minute? if 5 second granularity needed there will be 30 jobs every minute

@timgaunt

This comment has been minimized.

Show comment
Hide comment
@timgaunt

timgaunt May 10, 2017

This is also something we'd be interested in as the hacks we have in place at the moment are a little hampering

timgaunt commented May 10, 2017

This is also something we'd be interested in as the hacks we have in place at the moment are a little hampering

@LeifDC

This comment has been minimized.

Show comment
Hide comment
@LeifDC

LeifDC May 10, 2017

This would be a very useful feature!

LeifDC commented May 10, 2017

This would be a very useful feature!

@darrenbenn-dc

This comment has been minimized.

Show comment
Hide comment
@darrenbenn-dc

darrenbenn-dc May 10, 2017

This feature would be awesome!! 👍

darrenbenn-dc commented May 10, 2017

This feature would be awesome!! 👍

@burningice2866

This comment has been minimized.

Show comment
Hide comment
@burningice2866
Contributor

burningice2866 commented May 10, 2017

@thobanimadonsela

This comment has been minimized.

Show comment
Hide comment
@thobanimadonsela

thobanimadonsela Aug 30, 2017

Does anyone know when we can expect this release?

thobanimadonsela commented Aug 30, 2017

Does anyone know when we can expect this release?

@enrico-padovani

This comment has been minimized.

Show comment
Hide comment
@enrico-padovani

enrico-padovani Sep 2, 2017

This is a log awaited feature, we'd use it immediately!

enrico-padovani commented Sep 2, 2017

This is a log awaited feature, we'd use it immediately!

@heithvaldr1

This comment has been minimized.

Show comment
Hide comment
@heithvaldr1

heithvaldr1 Nov 25, 2017

Очень жду!

heithvaldr1 commented Nov 25, 2017

Очень жду!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment