Job Controls
Cancel Jobs
In the running UI for your Job, there will be a Cancel button:
(For Admins only) To cancel any Job in your Holistics workspace:
Go to Job Monitoring
Cancel the target Job(s)
- To cancel all Pending Jobs, click the Cancel Created Jobs on the top-right corner of the page
- To cancel a specific Job, click the Cancel button on the right end of a Job entry
How cancellation of Running Jobs works
Automatically cancel unused Jobs
This feature is currently in Beta!
In the Admin Settings page, Holistics offers the Unused Job Timeout setting that automatically cancel unused Jobs:
Demo
Explanation
- Unused Jobs: Jobs that are not being used by any user's browser
- For example: A user visits a Dashboard with 10 widgets and creates 10 Jobs, then closes their browser => Those 10 Jobs are unused.
Notes
- This auto cancellation only applies to Jobs in these Job Queues:
Report
Embed
Adhoc Query
- What if my users want to keep the Jobs running in the background (e.g. to warm up cache)?
- Implicitly keeping the Jobs running makes it hard to control the resources.
- Thus, if it's really necessary, please advise your users to do these instead:
- Run Holistics in multiple browser tabs
- Use Dashboard Preload
- Use Scheduled Deliveries
Disable Dashboard Auto-run
Disable Dashboard Auto-run also helps avoid spawning unnecessary Jobs.
Please refer to Disable Dashboard Auto-run.
Increase your default slots for specific Job Queues
This approach cannot be done from your side since this action will require our support engineer to adjust the queue size.
If you think that your current default slot (2 concurrent jobs for data transforms for example) is not enough for your operation, please contact us via support@holistics.io and we will process your request. Note that it may add additional billing/commercial terms to your Holistics subscription.
References:
Limit the Query Timeout of your Database Connection
Having a limit on the Query Timeout would help prevent slow queries from occupying the Job Queue for too long and block the other Jobs.
Please refer to this documentation to configure the Query Timeout of your Database Connection.
Example Scenario
Query Timeout can also help protect your Database resources from too much load.
If a query keeps timing out, it is best to optimize the query or quarantine it (e.g. by moving it to your personal workspace or deleting it) to avoid unnecessary load whenever opening the Report using that query.
Limit Number of Report Jobs Run Per User
Since the max concurrent jobs are being capped per queue, when user A purposely or accidentally farms multiple jobs, these jobs quickly take up all the available slots in the queue, causing other users unable to use the system.
To prevent this from happening, admins can set a limit on how many report jobs each user can run concurrently. You can find this setting in the Admin Settings page.
This Limit setting is most suitable when you have many Users using many different Reports.
Otherwise, Job De-duplication may apply and result in your Users waiting longer. See the explanation below.