azure - How can I have configuration per worker role _instance_ (not role) -


given: 1 worker role + several quartz.net jobs. quartz jobs host-agnostic , executed in worker role.

a worker role can scaled multiple instances.

the goal is: have ability define job run in instance @ runtime (or define configuration only, no code changes). example:

  • myrole instance 1: job1, job2, job3
  • myrole instance 2: job4,
  • myrole instance 3: job4,
  • myrole instance 4: job4,
  • myrole instance 5: job5, job6

in example job4 receives lot of load. i'd run on more instances. , want scalable @ runtime (or @ least via configuration, w/o code changes).

afaik not possible have azure configuration per instance (only per role itself). search online on similar issues haven't given results.

question: did have similar situation? best approach? other design advice appreciated. thanks.

this more of architectural problem 1 specific azure. common solution set "broker" each instance/process reaches out , asks individual workload. challenge, regardless of platform deploying solution how a) identify broker , b) ensure "state" information being managed broker persisted in case broker process dies.

the common approach address these concerns in azure use of blob lease on allows broker 'self elected' (the first process lease broker), , stores both address of broker , broker's state (metadata stored within blob). put logic assigning jobs broker in way best suits task distribution needs.


Comments

Popular posts from this blog

javascript - RequestAnimationFrame not working when exiting fullscreen switching space on Safari -

Python ctypes access violation with const pointer arguments -