Conversation
alejandromontero
force-pushed
the
Add/HDI-cluster-307
branch
from
c8a7d1c to
a13d173
Compare
fenech
left a comment
fenech
left a comment
There was a problem hiding this comment.
"Modify cluster 295" is true, but "Increase cluster 295 node count to 64" would give me a lot more information.
| clusterCostDisk="0.17" # 5TB/hr | ||
|
|
||
| resourceGroup="Default-Storage-SouthCentralUS" | ||
| resourceGroup="alojadlapremium" |
There was a problem hiding this comment.
Maybe it's right (I have no idea), but this looks like a typo since I would expect aloja adla.
There was a problem hiding this comment.
A resource group is a set of resources in Azure so we can easily manage them. The only one that was available was the one you see. It makes no difference at all and arranges all our clusters, both HDI and adla together for easier management
There was a problem hiding this comment.
Great, but all I'm saying is that alojadlapremium looks wrong, because aloja ends in an a and adla starts in an a, but there is only one a between them. Makes sense?
Since we are still reviewing config changes (did I mention that these have no place in a public repo?), I thought that I could at least try to help by pointing out a possible typo in the name of the resource group. If it's definitely right, then nothing to worry about.
There was a problem hiding this comment.
In our case "DLA" makes complete sense:
dla = data lake analytics
adla = azure data lake analytics
The command line of azure uses "az dla" y "az dls" not adla. Not only that but also one of our accounts is alojadw instead of alojaadw (Data Warehouse).
In essence, I wouldn't say it's a typo.
alejandromontero
force-pushed
the
Add/HDI-cluster-307
branch
from
a13d173 to
feca5bc
Compare
2 participants
No description provided.