Azure Data Factory
An Azure service for ingesting, preparing, and transforming data at scale.
10,681 questions
Scale up / scale down a self-hosted IR
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 28.999999999999996%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERS%3C/text%3E%3C/svg%3E)
Ravikiran Srini
20
Reputation points
In the para in the below link, it is mentioned that:
"When the processor and available RAM aren't well utilized, but the execution of concurrent jobs reaches a node's limits, scale up by increasing the number of concurrent jobs that a node can run. You might also want to scale up when activities time out because the self-hosted IR is overloaded"
I do not understand the second line. Why would we increase the concurrency count (scale up) if the IR is overloaded? Does it mean to say scale down?
{count} votes
-
Ravikiran Srini 20 Reputation points
2024-10-06T01:07:57.9166667+00:00 Ok, I understand that in the second scale-out, they mean to add more RAM and CPU. There are two different meanings of scale-out implied in a single para, which is confusing.
Please let me know if my understanding is correct.
Sign in to comment
Sign in to answer