Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quartz: do we understand how this works: none of the neon-cluster-operator jobs are being triggered? #1900

Open
jefflill opened this issue Apr 9, 2024 · 0 comments
Labels
bug Identifies a bug or other failure neon-kube Related to our Kubernetes distribution

Comments

@jefflill
Copy link
Collaborator

jefflill commented Apr 9, 2024

While testing https://github.com/nforgeio/neonCLOUD/issues/442 while running neon-cluster-operator locally on my workstation, I noticed that the related job class was not being executed.

I set breakpoints for all of the job class Execute() methods and manually edited the neonclusterjob resource to set all of the schedules to 0 1 * ? * * (once a minute). neon-cluster-operator reconciles the change and updates the job schedules just fine, but none of the breakpoints trigger after waiting 25 minutes.

I then tried restarting the operator again (in the debugger) and saw it reconcile the neonclusterjob resource but didn't see any of the breakpoints being hit after 10 minutes.

I'm not sure we understand how Quartz works. We should probably write some unit tests to investigate.

After we address this, we should follow up and complete these issues:

https://github.com/nforgeio/neonCLOUD/issues/442
#1899

@jefflill jefflill added bug Identifies a bug or other failure neon-kube Related to our Kubernetes distribution labels Apr 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Identifies a bug or other failure neon-kube Related to our Kubernetes distribution
Projects
None yet
Development

No branches or pull requests

1 participant