Updating jobs about stevejobs

[msavin]

You could do something like:

if (!JobsInternal.Utilities.collection.findOne({name: name})) {
     Jobs.run(JOB_ID, null, RUN_CONFIG);
} 

FYI - as @gary-menzel mentioned - there is a v3 on the way which will feature this.replicate so that each instance of the job has its own document. More info in CHANGES.md

https://github.com/msavin/SteveJobs...meteor.schedule.background.tasks.jobs.queue/tree/v3

[jmoseley]

That seems reasonable. Is V3 close to stable?

[jmoseley]

Oh I think another confounding factor is that this is a repeating job, so I do not end with this.success(), I end with this.reschedule(...).

export function registerJob({
  name,
  run,
}: {
  name: string;
  run: (args: RunArguments) => Promise<void>;
}) {
  console.info(`Registering ${name} job.`);

  Jobs.register({
    [name](args: RunArguments) {
      /* Forward context/params to 'run' method - execute in a fiber-aware await to
       allow regular async syntax in provided function */
      MeteorPromise.await(run.apply(this, args));
    },
  });
}

const RUN_CONFIG: RunConfig = {
  in: {
    minutes: 5,
  },
};

export const JOB_ID = 'job1';

async function runFunction(_args?: RunArguments) {
  const self: JobInstance = this;

  // ... do a bunch of stuff

  // Run the job again, so it keeps looping.
  self.reschedule(RUN_CONFIG);
}

registerJob({ name: JOB_ID, run: runFunction });
console.info(`Running ${JOB_ID} job.`);
Jobs.run(JOB_ID, null, RUN_CONFIG);

And the result is many entries in the job_data collection, all with the pending state.

[gary-menzel]

#29 may also be related - I believe there is a V3 being planned that will readdress how rescheduling works.

[msavin]

This is working as it should. The problem is, the server is executing Jobs.run(JOB_ID, null, RUN_CONFIG) every time it starts up. You only need to run it once to "jumpstart" it.

[jmoseley]

Oh that's interesting. Is there a way to check if that "jumpstart" has already been done? Allows me to ensure that the job is started as the code slides through different environments (and eventually to production).

[jmoseley]

And what's the easiest way to install V3?

[msavin]

I just pushed it - so run meteor update and you'll have it. Let me know how it goes. :)

[mazak]

Perfect!

[jmoseley]

Awesome thats great! Thanks for the speedy response and the support.

[jmoseley]

If you are curious, this is what I came up with to wrap it into a cron job.

My business logic lives in an async function the returns SUCCESS or RETRY and the wrappers in ^ do the work of rescheduling or replicating depending on the result. Also cancels the pending version on creation so the job can be updated with new code changes safely.

And I just call runRepeatingJob({ name: "jobName", job: myCoolFunction, args, repeatMinutes: 5 }) and the wrapper handles the rest. myCoolFunction does not need to know anything about the implementation.

[msavin]

@jmoseley thanks for sharing and glad you got it working. Unfortunately, I'm not up on the latest es6 practicers, but once I am I will be sure to take a look :)

[jmoseley]

Ah ya it's typescript, so might be hard to grok up front, but hopefully it helps someone else get started.

[gary-menzel]

@jmoseley Although I don't use TS, I found it useful. I have been using Promise a fair bit but somehow missed that there is a Meteor version available as a package. It looks like it makes working withMeteor.bindEnvironment much more seamless. Thanks for the link.