JobSchedule | 基于Quartz.net 的Job调度框架 | DevOps library

I have been looking into using JobRunr for starting background jobs on my Spring MVC application, as I really like the simplicity of it, and the ease of integrating it into an IoC container.

I am trying to create a simple test scheduled job that writes a line of text to my configured logger every minute, but I'm struggling to figure out how to get the JobRunr background job server to detect it and queue it up. I am not using Spring Boot so I am just using the generic jobrunr Maven artifact rather than the "Spring Boot Starter". My setup is as follows:

pom.xml

I have an app with a Switch that has to fire my JobService. I called two methods in setOnCheckedChangeListener of the Switch, one for register and one for unregister the job. It seems to work, like debug shows, but the the background work inside the onStartJob. What am I missing?

MemoNotificationService.kt

I have an AWS CLI cluster creation command that I am trying to modify so that it enables my driver and executor to work with a customized log4j.properties file. With Spark stand-alone clusters I have successfully used the approach of using the --files switch together with setting -Dlog4j.configuration= specified via spark.driver.extraJavaOptions, and spark.executor.extraJavaOptions.

I tried many different permutations and variations, but have yet to get this working with the Spark job that I am running on an AWS EMR clusters.

I use the AWS CLI's 'create cluster' command with an intermediate step that downloads my spark jar, unzips it to get at the log4j.properties packaged with that .jar. I then copy the log4j.properties to my hdfs /tmp folder and attempt to distribute that log4j.properties file via '--files'.

Note, I have also tried this without hdfs (specifying --files log4j.properties instead of --files hdfs:///tmp/log4j.properties) and that didn't work either.

My latest non-working version of this command (using hdfs) is given below. I'm wondering if anyone can share a recipe that actually does work. The output of the command from the driver when I run this version is:

Premise: I have a calendar-like system that allows the creation/deletion of 'events' at a scheduled time in the future. The end goal is to perform an action (send message/reminder) prior to & at the start of the event. I've done a bit of searching & have narrowed down to what seems to be my two most viable choices

• Unix Cron Jobs
• Bree

I'm not quite sure which will best suit my end goal though, and additionally, it feels like there must be some additional established ways to do things like this that I just don't have proper knowledge of, or that I'm entirely skipping over.

My questions:

• If, theoretically, the system were to be handling an arbitrarily large amount of 'events', all for arbitrary times in the future, which of these options is more practical system-resource-wise? Is my concern in this regard even valid?

• Is there any foreseeable problem with filling up a crontab with a large volume of jobs - or, in bree's case, scheduling a large amount of jobs?

• Is there a better idea I've just completely missed so far?

This mainly stems from bree's use of node 'worker threads'. I'm very unfamiliar with this concept and concerned that since a 'worker thread' is spawned per every job, I could very quickly tie up all of my available threads and grind... something, to a halt. This, however, sounds somewhat silly & possibly wrong(possibly indicative of my complete lack of knowledge here), & thus, my question.

Thanks, Stark.

I have an application that at 7AM need to check if there are some task during the day to display their notification, example of workflow: 7AM: check if there is any task for today -> found one at 5PM -> set a notification at 5PM

I have tried to implement Worker, JobScheduler, AlarmReceiver, Broadcast Receiver, JobService, but nothing will trigger if the app is not at least in background.

Any suggestion on what to implement to perform what i need? Thankyou!

EDIT: adding output for: adb shell dumpsys jobscheduler

I have created a .Net Core MVC project and understand that how the dependency injection works for our MVC controller as shown below, but same like I wanted to create an object for my own class by calling the same injected interface/class as a parameter.

I know I can specify .WithMisfireHandlingInstructionDoNothing() when building the trigger but some of my jobs are triggered via the IScheduler.TriggerJob() method, so without any triggers.

I can detect and log misfires in the ITriggerListener listener but how can I stop Quartz from trying to fire the job again? If I understand correctly .VetoJobExecution is not usable since the job has to be triggered successfully anyway.

Any other ideas?

Edit: my implementation

I am new to Android and working on this chat app where I want to change an Activity element based on a predetermined data on predetermined exact times. It doesn't have to work when app or phone is closed but I want to send notifications as well with the change. There is AlarmManager, JobScheduler, Handler, Timer, WorkManager but I am extremely confused about how they compare to each other. Which is the best option in this case?

While trying to find out why my android app (java) was not responding for the first 2-3 seconds after launching (UI elements were loaded, apart from menu options, but I could not click anything), I located the delay being caused by the command that schedules a task with JobScheduler.

Basically I have an App class that extends Application, and there I do set a task with JobScheduler that would run every 30 minutes and perform some action (update some information and provide notification if their value was changed).

After creating the Builder containing all details for that task, i run the command scheduler.schedule(info) and by commenting it out I found out that this is the reason my app is unresponsive for 2-3 seconds after launching.