yarn.scheduler.capacity.root.Marketing.acl_submit_applications=*
yarn.scheduler.capacity.root.Marketing.Advertising.acl_administer_queue=*
yarn.scheduler.capacity.root.Marketing.Advertising.acl_submit_applications=*
yarn.scheduler.capacity.root.Marketing.Advertising.capacity=30
yarn.scheduler.capacity.root.Marketing.Advertising.maximum-capacity=30
yarn.scheduler.capacity.root.Marketing.Advertising.minimum-user-limit-percent=100
yarn.scheduler.capacity.root.Marketing.Advertising.ordering-policy=fifo
yarn.scheduler.capacity.root.Marketing.Advertising.state=RUNNING
yarn.scheduler.capacity.root.Marketing.Advertising.user-limit-factor=1
yarn.scheduler.capacity.root.Marketing.capacity=40
yarn.scheduler.capacity.root.Marketing.maximum-capacity=100
yarn.scheduler.capacity.root.Marketing.minimum-user-limit-percent=100
yarn.scheduler.capacity.root.Marketing.ordering-policy=fifo
yarn.scheduler.capacity.root.Marketing.queues=Advertising,Sales
yarn.scheduler.capacity.root.Marketing.Sales.acl_administer_queue=*
yarn.scheduler.capacity.root.Marketing.Sales.acl_submit_applications=*
yarn.scheduler.capacity.root.Marketing.Sales.capacity=70
yarn.scheduler.capacity.root.Marketing.Sales.maximum-capacity=70
yarn.scheduler.capacity.root.Marketing.Sales.minimum-user-limit-percent=100
yarn.scheduler.capacity.root.Marketing.Sales.ordering-policy=fifo
yarn.scheduler.capacity.root.Marketing.Sales.state=RUNNING
yarn.scheduler.capacity.root.Marketing.Sales.user-limit-factor=1
yarn.scheduler.capacity.root.Marketing.state=RUNNING
yarn.scheduler.capacity.root.Marketing.user-limit-factor=1
yarn.scheduler.capacity.root.queues=Engineering,Marketing,Support,default
yarn.scheduler.capacity.root.Support.acl_administer_queue=*
yarn.scheduler.capacity.root.Support.acl_submit_applications=*
yarn.scheduler.capacity.root.Support.capacity=20
yarn.scheduler.capacity.root.Support.maximum-capacity=24
yarn.scheduler.capacity.root.Support.minimum-user-limit-percent=100
yarn.scheduler.capacity.root.Support.ordering-policy=fifo
yarn.scheduler.capacity.root.Support.queues=Services,Training
yarn.scheduler.capacity.root.Support.Services.acl_administer_queue=*
yarn.scheduler.capacity.root.Support.Services.acl_submit_applications=*
yarn.scheduler.capacity.root.Support.Services.capacity=80
yarn.scheduler.capacity.root.Support.Services.maximum-capacity=80
yarn.scheduler.capacity.root.Support.Services.minimum-user-limit-percent=100
yarn.scheduler.capacity.root.Support.Services.ordering-policy=fifo
yarn.scheduler.capacity.root.Support.Services.state=RUNNING
yarn.scheduler.capacity.root.Support.Services.user-limit-factor=1
yarn.scheduler.capacity.root.Support.state=RUNNING
yarn.scheduler.capacity.root.Support.Training.acl_administer_queue=*
yarn.scheduler.capacity.root.Support.Training.acl_submit_applications=*
yarn.scheduler.capacity.root.Support.Training.capacity=20
yarn.scheduler.capacity.root.Support.Training.maximum-capacity=20
yarn.scheduler.capacity.root.Support.Training.minimum-user-limit-percent=100
yarn.scheduler.capacity.root.Support.Training.ordering-policy=fifo
yarn.scheduler.capacity.root.Support.Training.state=RUNNING
yarn.scheduler.capacity.root.Support.Training.user-limit-factor=1
yarn.scheduler.capacity.root.Support.user-limit-factor=1
多租戶的驗證
下面由不同的用戶 dev1、qa1、adv1、sal1、serv1、tr1 分別提交任務(wù)，在 ResourceManager UI 的 Scheduler 視圖可以監(jiān)控到任務(wù)被分配到不同的隊列。
用戶 dev1 提交的作業(yè)分配到 Development 隊列
用戶 qa1 提交的作業(yè)分配到 QA 隊列
用戶 adv1 提交的作業(yè)分配到 Advertising 隊列
用戶 sal1 提交的作業(yè)分配到 Sales 隊列
用戶 serv1 提交的作業(yè)分配到 Services 隊列
用戶 tr1 提交的作業(yè)分配到 Training 隊列
同時可以監(jiān)控到隊列資源的使用情況，綠色是占用的資源，黃色是已經(jīng)超過 Capacity 屬性的定義值，灰色是已經(jīng)到達(dá) Max Capacity 的設(shè)置。從視圖可以看出 Engineering.Development 隊列、Marketing.Advertising 隊列和 Support.Training 隊列目前已經(jīng)超過 Capacity 屬性的定義值，正在占用父隊列的資源，但還沒有到達(dá) Max Capacity 屬性的定義值。
圖 13. IBM BigInsights 多租戶的驗證
