Harvester / Add property to turn off scheduling #7217
Conversation
…vester scheduler. Add some more precise doc links.
|
SonarCloud Quality Gate failed.
|
| label: "systemInformation" | ||
| }, | ||
| { | ||
| key: "env" |
There was a problem hiding this comment.
The final goal for this I guess is to have multiple instances 1 with the scheduler enabled and the others disabled.
I'm not sure how useful is to display this information in such scenario as depending on the instance accessed the value displayed will be different.
Also this kind of stuff raises some questions, for example what happens in the node with the scheduler enabled fails? Should be implemented in a future pull request some mechanism so other node picks up the scheduler, using JMS messages or similar?
There was a problem hiding this comment.
The final goal for this I guess is to have multiple instances 1 with the scheduler enabled and the others disabled.
Yes.
I'm not sure how useful is to display this information in such scenario as depending on the instance accessed the value displayed will be different.
Sure, but at least if you access the instance with scheduler on by its url you can check that the settings is properly enabled.
Also this kind of stuff raises some questions, for example what happens in the node with the scheduler enabled fails? Should be implemented in a future pull request some mechanism so other node picks up the scheduler, using JMS messages or similar?
We are not here yet, but yes this is some further improvement we could plan.
|
In #7337 |
Related to #6990
When running in a scaled environment, user may want to only have one instance taking care of scheduled harvesting tasks. Adding a config property to turn it off/on using
-Dharvester.scheduler.enabled=false. All instances can run a manually triggered harvesting task.If set, the config property is also available in the admin > info panel
Also improve: