Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Consider about design 2 job execution type of ElasticJob-Lite
See original GitHub issueThere is a configuration item monitorExecution in ElasticJob-Lite, which can enable the job record and monitor job, and provide precondition for failover.
I want discuss maybe we can split job as two different way.
If monitorExecution enabled, the job can be failover, misfire and DAG management.
So we need to create the new concept if them.
If monitorExecution disabled, the job should be lightweight and short interval;
If monitorExecution enabled, the job has more features and can be manageable.
I have no idea of the concept name, any idea?
Issue Analytics
- State:
- Created 3 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@Technoboy- tboy has written some design doc of DAG, may publish in other issue when he finished.
execute process tracing of complex job flow is very important for users.
e.g job of DAG or Sharding