Package nl.esciencecenter.xenon.schedulers

Interface SchedulerAdaptorDescription

    • Method Summary

      All Methods Instance Methods Abstract Methods 
      Modifier and Type Method Description
      boolean isEmbedded()
      Is this an embedded scheduler ? Embedded schedulers are implemented inside the Xenon process itself.
      boolean supportsBatch()
      Does this Scheduler support the submission of batch jobs ? For batch jobs the standard streams of the jobs are redirected from and to files.
      boolean supportsInteractive()
      Does this Scheduler supports the submission of interactive jobs ? For interactive jobs the standard streams of the job must be handled by the submitting process.
      boolean usesFileSystem()
      Does this Scheduler create a FileSystem to support the submission of jobs ? Many scheduler implementations use a FileSystem internally to handle job submission, for example to store submission scripts or handle the standard I/O streams of a process.

    • Method Detail

      • isEmbedded

        boolean isEmbedded()
        Is this an embedded scheduler ? Embedded schedulers are implemented inside the Xenon process itself. Therefore this process needs to remain active for its jobs to run. Ending an online scheduler will typically orphan or kill all jobs that were submitted to it. Non-embedded schedulers do not need to remain active for their jobs to run. A submitted job will typically be handed over to some external server that will manage the job for the rest of its lifetime.
        Returns:
        if this scheduler is embedded.

      • supportsBatch

        boolean supportsBatch()
        Does this Scheduler support the submission of batch jobs ? For batch jobs the standard streams of the jobs are redirected from and to files.
        Returns:
        if this scheduler supports the submission of batch jobs ?

      • supportsInteractive

        boolean supportsInteractive()
        Does this Scheduler supports the submission of interactive jobs ? For interactive jobs the standard streams of the job must be handled by the submitting process. Failing to do so may cause the job to hang indefinitely.
        Returns:
        if this scheduler supports the submission of interactive jobs ?

      • usesFileSystem

        boolean usesFileSystem()
        Does this Scheduler create a FileSystem to support the submission of jobs ? Many scheduler implementations use a FileSystem internally to handle job submission, for example to store submission scripts or handle the standard I/O streams of a process. This FileSystem can optionally be retrieved by the user to perform other tasks, such as staging in and output data of the job. To do so use Scheduler.getFileSystem() method.
        Returns:
        does this Scheduler create a FileSystem to support the submission of jobs ?