Examples of org.apache.ode.scheduler.simple.SimpleScheduler

org.apache.ode.scheduler.simple.SimpleScheduler

A reliable and relatively simple scheduler that uses a database to persist information about scheduled tasks. The challange is to achieve high performance in a small memory footprint without loss of reliability while supporting distributed/clustered configurations. The design is based around three time horizons: "immediate", "near future", and "everything else". Immediate jobs (i.e. jobs that are about to be up) are written to the database and kept in an in-memory priority queue. When they execute, they are removed from the database. Near future jobs are placed in the database and assigned to the current node, however they are not stored in memory. Periodically jobs are "upgraded" from near-future to immediate status, at which point they get loaded into memory. Jobs that are further out in time, are placed in the database without a node identifer; when they are ready to be "upgraded" to near-future jobs they are assigned to one of the known live nodes. Recovery is rather straighforward, with stale node identifiers being reassigned to known good nodes. @author Maciej Szefler ( m s z e f l e r @ g m a i l . c o m )

      odeProperties.put("ode.scheduler.queueLength", "100" );
      odeProperties.put("ode.scheduler.immediateInterval", "30000" );
      odeProperties.put("ode.scheduler.nearFutureInterval", "600000" );
      odeProperties.put("ode.scheduler.staleInterval", "100000" );
      
        SimpleScheduler scheduler = new SimpleScheduler(new GUID().toString(),
                                            new JdbcDelegate(_db.getDataSource()),
                                                        odeProperties );
        scheduler.setExecutorService(_executorService);
        scheduler.setTransactionManager(_txMgr);


        return scheduler;
    }

Examples of org.apache.ode.scheduler.simple.SimpleScheduler

Related Classes of org.apache.ode.scheduler.simple.SimpleScheduler