I know Hangfire has a logic of auto re-queue jobs that have been running for >30 minutes.
But I have a job that will run for >30 minutes and I don't want any auto-retry.
Meanwhile, I have some jobs that need auto-retry.
Is there anything to configure an individual job's auto-retry-timeout value?
e.g. I manually configure job A's value to 24 hours so it can run for 24 hours without any timeout retry while other jobs remain the same and are auto re-queued when their execution time exceeded 30 minutes.
Related
I have three SQL Agent jobs, one for each of three registries being managed. These go off on a staggered schedule every two hours (i.e. Reg 1 at 9am, 3pm; Reg 2 at 11am, 5pm; Reg 3 at 1pm, 7pm).
In most every circumstance, it takes less than two hours for one of these jobs to run. However, if it is taking longer than expected, I do NOT want the other job to run. So, if Reg 1's 9am run is taking more than 2 hours, I do not want Reg 2's 11am job to run UNTIL Reg 1's job is completed.
How can I work this conditional run functionality in? I am not seeing anything in the schedules properties of the job. Let me know if you need more clarification!
Thanks!!
What should be the ramp up time when i need to send 10k request[each request has 6http subsequent calls], I need to send 1 request per minute. and i need to send one request for every 20seconds
Your post contains 4 questions which are mutually exclusive so I provide a generic answer:
If you want to send X requests at exactly the same moment:
Add X thread (virtual users) to Thread Group
Add Synchronizing Timer to the request and set Number of Simultaneous Users to Group by to X
If you want to send 1 request per minute - add Constant Throughput Timer to your request and set Target Throughput to 1
If you want to send 1 request each 20 seconds - the same approach as for point 2 but Target Throughput will be 3
Ramp-up is the time period for starting virtual users, normally normal people use it for gradual load increase, for example if you have 10 users and 10 seconds ramp-up JMeter will start 1 user each second, if you have 10 users and 20 seconds ramp-up JMeter will start each user each 2 seconds, etc.
I have a recurring Hangfire job that runs daily. As part of the logic the job fetches entities created within the last 24 hours. It uses DateTime.Now in the logic. I realize that this is not a robust design in the case that the job fails and it is run several days later. Is there any way I can pass the current time as a parameter to a recurring job? Or do I need to rewrite the logic to be independent of the current time? I have tried RecurringJob.AddOrUpdate(() => FooAction.Execute(GetTime()), cronSchedule); but as expected that just always passses the time that the recurring job was created.
One idea would be to skip the recurring job and create a regular Hangfire job instead. The last thing the job should do is create a new job and pass the specified time as parameter. But I would prefer to use a recurring job if I can.
"You could have a recurring job run that is responsible for creating non-recurring jobs, and passing the current time into those."
From comment by #mason.
How can I stop a background job at 14 minutes or after?
I basically have sub queries that can last 15 seconds Max and I'd like to stop them at 14m 15sec maximum so I can make sure they all completely terminate. I don't know how to implement a timer on a background job
I have exceeded the daily limit for the number of import to a specific table.
(Max=1000 imports according to the documentation here: https://developers.google.com/bigquery/quota-policy#import )
I would like to know when exactly does the quota reset back to 0? Is it 24hours after I exceeded the quota, or is it at a specific time?
As of this July 18 2014, all daily quotas are partially replenished every 10 minutes or so.
The first time you run a load job to a table (or if you haven't done so in a while) you'll get 1000 loads. Every few minutes, the quota will partially replenish, up to a maximum of 1000 available.
While this sounds complex, it means that you never get in a situation where you run out of daily quota and have to wait up to 24 hours for quota to reset. Instead, if you run out of quota you can start running jobs fairly soon thereafter (as long as you stay within the replenishment rate).
Hope that is helpful.