node "n1"{
fastname "s1"
pool "" "n1" "s1" "app2" "sort"
resource disk "/orch/n1/d1"{}
resource disk "/orch/n1/d2" {"bigdata"}
resource scratchdisk"/temp"{"sort"}
}
node "n2"{
fastname "s2"
pool "" "n2" "s2" "app1" "sort"
resource disk "/orch/n2/d1"{}
resource disk "/orch/n2/d2" {"bigdata"}
resource scratchdisk"/temp"{"sort"}
}
node "n3"{
fastname "s3"
pool "" "n3" "s3" "app1" "sort"
resource disk "/orch/n3/d1"{}
resource scratchdisk"/temp"{}
}
node "n4"{
fastname "s4"
pool "" "n4" "s4" "app1" "sort"
resource disk "/orch/n4/d1"{}
resource scratchdisk"/temp"{}
}
My queries are:
1.Please justify the conductor names and section leaders in this scenario.
2.If last three fastnames are same say"s2",how the conductor scenario changes?
3.Is the "bigdata" specified here the user defined resource pool or reserved name for resource pool?
4.What is the default node pool here and changes happen If I do not specify named pools(n1,s1,app1,sort)?
Please correct me If I had posted any question wrong.
![Smile :)](./images/smilies/icon_smile.gif)
Thanks in advance
Kiran