@Sandeep Nemuri @Arti Wadhwani Please suggest. ... View more

@Mohammad Hamdan Here is content of capacity scheduler. Please suggest: yarn.scheduler.capacity.maximum-am-resource-percent=0.2 yarn.scheduler.capacity.maximum-applications=10000 yarn.scheduler.capacity.node-locality-delay=40 yarn.scheduler.capacity.root.accessible-node-labels=* yarn.scheduler.capacity.root.acl_administer_queue=* yarn.scheduler.capacity.root.capacity=100 yarn.scheduler.capacity.root.default.acl_submit_applications=* yarn.scheduler.capacity.root.default.capacity=25 yarn.scheduler.capacity.root.default.maximum-capacity=50 yarn.scheduler.capacity.root.default.state=RUNNING yarn.scheduler.capacity.root.default.user-limit-factor=2 yarn.scheduler.capacity.root.queues=default,hs2,longrun,sqoop,talend yarn.scheduler.capacity.queue-mappings=u:talenduser:talend,u:dbenefi:longrun,u:sqoop:sqoop yarn.scheduler.capacity.queue-mappings-override.enable=false yarn.scheduler.capacity.root.default.maximum-am-resource-percent=1 yarn.scheduler.capacity.root.hs2.acl_submit_applications=* yarn.scheduler.capacity.root.hs2.capacity=25 yarn.scheduler.capacity.root.hs2.maximum-am-resource-percent=0.4 yarn.scheduler.capacity.root.hs2.maximum-applications=500 yarn.scheduler.capacity.root.hs2.maximum-capacity=100 yarn.scheduler.capacity.root.hs2.ordering-policy=fair yarn.scheduler.capacity.root.hs2.ordering-policy.fair.enable-size-based-weight=true yarn.scheduler.capacity.root.hs2.state=RUNNING yarn.scheduler.capacity.root.hs2.user-limit-factor=4 yarn.scheduler.capacity.root.longrun.acl_submit_applications=* yarn.scheduler.capacity.root.longrun.capacity=15 yarn.scheduler.capacity.root.longrun.maximum-capacity=15 yarn.scheduler.capacity.root.longrun.state=RUNNING yarn.scheduler.capacity.root.longrun.user-limit-factor=1 yarn.scheduler.capacity.root.sqoop.acl_submit_applications=* yarn.scheduler.capacity.root.sqoop.capacity=10 yarn.scheduler.capacity.root.sqoop.maximum-am-resource-percent=1 yarn.scheduler.capacity.root.sqoop.maximum-capacity=100 yarn.scheduler.capacity.root.sqoop.state=RUNNING yarn.scheduler.capacity.root.sqoop.user-limit-factor=10 yarn.scheduler.capacity.root.talend.acl_submit_applications=* yarn.scheduler.capacity.root.talend.capacity=25 yarn.scheduler.capacity.root.talend.maximum-am-resource-percent=0.4 yarn.scheduler.capacity.root.talend.maximum-applications=500 yarn.scheduler.capacity.root.talend.maximum-capacity=100 yarn.scheduler.capacity.root.talend.ordering-policy=fair yarn.scheduler.capacity.root.talend.ordering-policy.fair.enable-size-based-weight=true yarn.scheduler.capacity.root.talend.state=RUNNING yarn.scheduler.capacity.root.talend.user-limit-factor=4 ... View more

amshare value is 0.4 i.e. 40%. Whats the meaning of -1.0f? I did not get. ... View more

Please find attached RM UI and RM Scheduler screenshou. Will attach RM logs soon. Please suggest.rm-scheduler.png rm-ui.png ... View more

@Mohammad Hamdan Min container size is 4GB and max container size is 8GB. ... View more

@Vipin Rathor I am logging in using bhushan-kandalkar user but in Zeppelin Notebook UI, I am still getting 'bhushan-kandalkar@test.com' user for every notebook permission. ... View more

@Felix Albani @Vipin Rathor I performed all these steps. I can see that user 'bhushan-kandalkar' is able to view notebooks created by 'bhushan-kandalkar@test.com' user. That's good news. But in Zeppelin Notebook UI, I am still getting 'bhushan-kandalkar@test.com' user. Attached screenshot notebook-permission.png. I am not getting ''bhushan-kandalkar' user. Also, when I share notebook to other user, that notebook is removed from the user who has shared that notebook. That should not happen. Please suggest. ... View more

Thanks @Felix Albani I already did that. But note permission for every notebook is still showing 'bhushan-kandalkar@test.com' as owner, reader and writer. Also, when I tried to change owner name to 'bhushan-kandalkar' its giving permission denied error. Please suggest. ... View more