locked
Running job calls Activation Filter RRS feed

  • Question

  • Hi all,

    we are currently implementing our own Activation Filter, for maintenance, license and fairshare purposes.

    Currently we have the following problem that the activation filter gets called multiple times by a job with multiple tasks. E.g. 4 Tasks, 9 calls.
    So there is obviously no correlation between # of tasks and queries.

    What is causing this and what is the purpose for that?
    JH
    Tuesday, March 16, 2010 3:16 PM

Answers

  • There is no correlation between the number of tasks in a job and the number of times the activation filter gets called for that job. The activation filter gets called everytime for a job that the scheduler thinks it can allocate new resources to that job.

    So, for a queued job when the scheduler finds that it has enough resources for the job, it calls the activation filter before starting the job on those resources. If the activation filter passes the job, the scheduler starts the job on those resources. If the activation filter does not pass the job because it does not have enough licesnses or some other reason, the scheduler does not start the job. However, in the next scheduling pass it will look at that job again and if it still has enough resources for the job it will call the activation filter with that job again. So, the number of times the activation filter gets called for a job, depends more on the length of time the job can not run because the activation filter keeps turning it down.

    In addition, if a running job grows to more resources, the activation filter will get called for that job again.

    Please do let us know if this clarifies your question and if you have any more on this topic.

    Tuesday, March 30, 2010 6:53 PM
    Moderator

All replies

  • There is no correlation between the number of tasks in a job and the number of times the activation filter gets called for that job. The activation filter gets called everytime for a job that the scheduler thinks it can allocate new resources to that job.

    So, for a queued job when the scheduler finds that it has enough resources for the job, it calls the activation filter before starting the job on those resources. If the activation filter passes the job, the scheduler starts the job on those resources. If the activation filter does not pass the job because it does not have enough licesnses or some other reason, the scheduler does not start the job. However, in the next scheduling pass it will look at that job again and if it still has enough resources for the job it will call the activation filter with that job again. So, the number of times the activation filter gets called for a job, depends more on the length of time the job can not run because the activation filter keeps turning it down.

    In addition, if a running job grows to more resources, the activation filter will get called for that job again.

    Please do let us know if this clarifies your question and if you have any more on this topic.

    Tuesday, March 30, 2010 6:53 PM
    Moderator
  • There is no correlation between the number of tasks in a job and the number of times the activation filter gets called for that job. The activation filter gets called everytime for a job that the scheduler thinks it can allocate new resources to that job.

    So, for a queued job when the scheduler finds that it has enough resources for the job, it calls the activation filter before starting the job on those resources. If the activation filter passes the job, the scheduler starts the job on those resources. If the activation filter does not pass the job because it does not have enough licesnses or some other reason, the scheduler does not start the job. However, in the next scheduling pass it will look at that job again and if it still has enough resources for the job it will call the activation filter with that job again. So, the number of times the activation filter gets called for a job, depends more on the length of time the job can not run because the activation filter keeps turning it down.

    In addition, if a running job grows to more resources, the activation filter will get called for that job again.

    Please do let us know if this clarifies your question and if you have any more on this topic.

    Tuesday, March 30, 2010 6:53 PM
    Moderator
  • In addition, if a running job grows to more resources, the activation filter will get called for that job again.

    I think the above point explains the seen behavior. We are going to test that.

    Thanks for your answer.


    JH
    Wednesday, March 31, 2010 7:20 AM