Comments (3)
Is it safe to prune the beats w/o negatively affecting the jobs?
It is safe to prune beats that are more than a minute old. The UI relies on beats for a lot of what it displays, but it will recover after a few seconds if you delete all the beats.
A sweeper that's independent of the pruner.
Separate configuration for this could work. Currently beat pruning isn't configurable at all, which may be an issue for limited databases (i.e. entry tier heroku which only allows 10,000 rows).
If you were to enable pruning with a really long history (months, years) you would retain all of the jobs and get the automatic beat pruning.
from oban.
Yeah, we're on the hobby Heroku plan and we're about to hit the 10M record limit. Enabling a long history should do the trick. Thanks!
from oban.
Glad that will work!
If there is somewhere in the docs you'd have liked/expected to see this info, let me know (or open a PR 💛).
from oban.
Related Issues (20)
- Oban bringing app down on Prod with error (expected :repo to implement Ecto.Repo, got: MyApp.Repo) HOT 2
- `MatchError` on a DB transaction in `Oban.Peers.Postgres` HOT 2
- allow phoenix_html 4.0 in oban_web HOT 1
- Selecting jobs in Oban Web UI throws exception HOT 8
- Behaviour check in config validation fails with non-standard Repo module HOT 3
- Introduce global timeouts for workflows HOT 2
- Queue allowlist/denylist support for Lifeline Plugin HOT 1
- Oban Pro v1.3.1 Workflows jobs not moving to executing state HOT 16
- Oban with postgres fails when elixir time_zone_database is set to Tzdata.TimeZoneDatabase HOT 1
- Oban.Pro.Workers.Batch not executing callbacks when there is only one job in the batch HOT 1
- Potentially bug in handling DB errors in `Oban.Peers.Postgres` HOT 2
- Seeing High CPU Usage with Oban Table Partitioned HOT 12
- Overriding Worker.new results in a compilation warning HOT 2
- Oban Pro: jobs get stuck in executing and become orphans HOT 20
- Structs cannot be passed to Job.new HOT 3
- Notifier logs after upgrading to 2.17.4 HOT 18
- Upgrading to Oban 2.17.4 from 2.17.3 fails compilation step with `no function clause matching in Ecto.Query.with_cte/3 ` HOT 1
- Oban 2.17.4 update MATERIALIZED syntax error HOT 3
- Oban Web is refreshing the page constantly HOT 1
- Unclear docs for `perform/1` callback in case of an unhandled exception, exit or throw HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from oban.