job-scheduler | Open Distro for Elasticsearch Job Scheduler | Cron Utils library

I have an image analysis pipeline with parallelised steps. The pipeline is in python and the parallelisation is controlled by dask.distributed. The minimum processing set up has 1 scheduler + 3 workers with 15 processes each. In the first short step of the analysis I use 1 process/worker but all RAM of the node then in all other analysis steps all nodes and processes are used.

The admin will install HTCondor as a scheduler for the cluster.

In order order to have my code running on the new setup I was planning to use the approach showed in the dask manual for SGE because the cluster has a shared network files system.

I have checked most similar questions, and don't find the answer.So I can only post a new question.

I can successfully run my application without errors, but the rest api I write can't be access correctly.I have compared my launch log to the official tutorials, then I have found out I don't have the similar log below:

Okay so I am not able to find any documentation or useful web pages about this. Help me StackOverflow, you're my only hope.

Okay so originally my JobScheduler looks like this:

I have a module with no activity in it, its Job-scheduler or Service is created by a BroadcastReceiver (android.intent.action.BOOT_COMPLETED).

As per docs its mentioned that performance-monitoring "Starts when the app's FirebasePerfProvider ContentProvider completes its onCreate method and stops when the first activity's onResume() method is called. If the app was not cold-started by an activity (for example, by a service or broadcast receiver), no trace is generated."

So how to start performance-monitoring for apps without activities ?

I want to create a Report Scheduler to send the email with attach report automatically based on timings defined by User.

User can specify the Time and Occurrence of Report, once it is saved scheduler need to run on that specific time/day based on settings defined, also every user is independent to define its own settings.

I had taken reference from below SO answer

How to reschedule Quartz job scheduler in C# dynamically from database?

I use the docker-compose.override.yml to override my docker services in development and specifically reference the docker-compose.yml file when deploying to more production like environments much like this workflow.

If I have a service say my-job-scheduler, I don't want that to run in development so would prefer to include something in my docker-compose.override.yml file that tells docker-compose:

• Dont start this service; or
• Immediately stop this service

Is there a good pattern to do this?

I just started to create Quartz Scheduled Jobs in a dynamic way. So there is a QuartzConfig class where I create a SchedulerFactoryBean, JobDetailFactoryBean and CronTriggerFactoryBean. Wherein the Job and CronTrigger beans are prototype ones.

I am using MVP pattern in My Android application. My requirement is

1. Sync captured data when user clicks 'Sync' button

2. Job-scheduler who will invoke the background service at midnight and sync data with server even though the app is not running.

The flow for both scenarios is:

1)Sync captured data when user clicks 'Sync' button

• getPresenter().notifySyncBtnPressed() will be called

• notifySyncBtnPressed() will instruct the Model by calling mModel.sync()

• Sync from Model has entire implementation of fetching data from DB, upload it to server and notify result to Presenter
• Presenter then notify to View by calling getView().notifySyncFinished()

Note: This flow is clear to me - suggest improvements if needed

2) Job-scheduler who will invoke the background service( Please provide your clarification here)

• BroadcastReceiver will invoke Service class which extends IntentService
• Create model object (IModel model = new Model()) and call model.sync() from onHandleIntent().
• Since there is no UI, no need to invoke presenter. and no need to notify the status.
• Service will get killed once sync operation is done.

Please suggest,

1. is it the right way to call Model (Repository) instance from Service class?

2. I am also confuse between Model layer and Repositiry layer, is there any difference in Model layer and Repository layer here in MVP.