I submitted job to slurm and my job completed successfully.
After one hour/10 mins, i want to know the cpu time and wait time of my job?
How to know that ??
Please help me
suchetan
Related
When I run a job with Kitchen.bat, the job takes 100 seconds to start and I find the following line in the logs:
ERROR [KarafLifecycleListener] The Kettle Karaf Lifecycle Listener failed to execute properly after waiting for 100 seconds. Releasing lifecycle hold, but some services may be unavailable.
Is there a way to speed up the job start-up time?
Thanks
Is it possible to reschedule failed jobs in hangfire? And Is there any way to clear the failed job queue after the success?
How is it possible?
Jobs will be cleared automatically by hangfire after one day (by default).
https://discuss.hangfire.io/t/how-to-configure-the-retention-time-of-job/34/2?u=odinserj
See hangfire documentation about dealing with exceptions occurs during jobs execution
http://docs.hangfire.io/en/latest/background-processing/dealing-with-exceptions.html
I'm running into a weird issue with Pentaho 7.1. I run a job that I created and it runs perfectly and quickly the first time I run it.
The job is an ETL Job consisting of a Start widget, 7 Transformations running in a sequence, and a Success widget.
I'm confused as to why the job runs once, and when I try to run it again it says "Spoon - Starting job..." and then the job just hangs.
If I delete the job and I create a brand new one, I am then able to run the job once and I am stuck again with the job no longer able to run after that. I don't understand why the job keeps hanging after it gets executed once, and it is then 100% broken after a Successful run...
I turned up the logging in Pentaho 7.1 Spoon, and it shows this continuously...
2018/08/14 17:30:24 - Job1 - Triggering heartbeat signal for
ported_jobs at every 10 seconds 2018/08/14 17:30:34 - Job1 -
Triggering heartbeat signal for ported_jobs at every 10 seconds
2018/08/14 17:30:44 - Job1 - Triggering heartbeat signal for
ported_jobs at every 10 seconds 2018/08/14 17:30:54 - Job1 -
Triggering heartbeat signal for ported_jobs at every 10 seconds
I can't seem to put my finger on why this happening.
Any help is appreciated
Probable answer: Check that your transformations are not opening the same database for input and output. A quick check may to run the first transformation directly (without the job) and see if it locks.
Happened because the server db you want to update are slow to respond. Probably high CPU and RAM. I tried to increase the RAM and CPU for the db server, now my job runs okay.
I have a SQL Agent Job that shows as idle in the Activity Monitor but the time duration keeps increasing.
The job seems to have stopped as I've tried stopping it manually and SQL advises the job isn't running.
SysJobActivity doesn't have a stop_execution_date for the job
The job has 5 steps and the last step didn't complete - the server rebooted during the execution of this step.
Is the job ok to leave in it's current state? The duration will forever keep increasing.
Thanks
Job History
Activity Monitor
Job History - Updated
After the comments and viewing the screenshots I think I know what is going on:
The job duration is reported by what is in the msdb..sysjobhistory
The reboot during the job caused a problem (perhaps the power was killed to the box so it couldn't log properly?) so the job never really failed or finished and not properly recorded into the sysjobhistory.
It's not showing up in sp_who which means it is NOT running
I suspect it's probably OK to leave the job just 'running' forever. But I would suggest clearing that up so some other poor DBA isn't scratching his head. You could:
Manually edit the msdb..sysjobhistory which is scary and I wouldn't.
I bet start and stop the job and now it will report OK
Delete the job and history via the GUI and remake it (script it out first!)
I'm working on a workflow that has both Hive and Java actions. Very often we have been noticing that there is a few minutes delay between Java action start time and the job submission time. We don't see that with Hive jobs, meaning Hive jobs seem to be submitted almost immediately after they are started. The Java jobs do not do much and so they finish successfully in seconds after they are submitted but the time between start and submission seem to be very night ( 4 -5 minutes). We are using fair scheduler and the there are enough mapper/reducer slots available. But still even if it's a resource problem the Hive jobs should also show delay between start and submission but they don't ! Java jobs are very simple jobs and they don't process any files etc and basically used to call a web service and they spawn only single mapper and no reducers where are the Hive jobs creates hundreds of mapper/reducer tasks but still there is not delay between start and submission. We are not able to figure out why oozie is not submitting the Java job immediately. Any ideas?