Versions Compared

Old Version 6

changes.mady.by.user Nitin Beri

Saved on

compared with

New Version Current

changes.mady.by.user Nitin Beri

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Corrected links that should have been relative instead of absolute.

Adeptia checks available After user has enabled Resource-Based-Round-Robin allocation of jobs, Adeptia would check for the available resources on every node of the cluster before allocating a job in round-robin method. In other words, Adeptia system will first check the Whereas, in a normal round-robin method, system allocates the job to the next node in sequence without checking for availability of the resources on every node before allocating the job to the node next in sequence. If that node. After enabling this feature, if resources are not available on that node, it will move to the next node and check again before without allocating the job . In case there is no resource available in any of the node of the cluster, then system will wait for the time set in (after logging a notification in kernel logs file), and check the next node in the sequence for allocating the job. To enable resource-based allocation in Clustering:

  1. Go to ...\AdeptiaSuite-6.9\AdeptiaServer\ServerKernel\etc\cluster.
  2. Open cluster.properties file.
    3. Change the value of cluster.load.balance.policy from Round-Robin to Resource-Based-Round-Robin. 
    That is, change cluster.load.balance.policy=Round-Robin to
    cluster.load.balance.policy=Resource-Based-Round-Robin
     Image Removed
  3. Save the file.
  4. Login to Adeptia Suite.
  5. Go toto Administer > Setup> Application Settings.
  6. From Application Settings, go to Update System Properties > Load Management.In Load Management, set the threshold and waiting time in the relevant properties.
    Image Removed > Cluster and Queue Processor Configuration.
  7. Write Resource-Based-Round-Robin in the value box for cluster.load.balance.policy property.

    Image Added

  8. Click Save.
  9. Restart Kernel and & WebRunner.

    In case there is no resource available in any of the node of the cluster, then system will wait for the time set in abpm.node.resourceavailability.check.waiting.period property. Users can view the notification of unsuccessful allocation of the job to a node in the kernel logs file.

  10. To set the threshold and waiting time go to Administer > Setup> Application Settings
  11. From Application Settings, go to Update System Properties > Load Management > System Throttling.
    Image Added