This sounds like a bug, and both values are removed in newer Ambari versions. https://issues.apache.org/jira/browse/AMBARI-13232 Could you remove the following two values and try to restart the RM: yarn.scheduler.capacity.root.accessible-node-labels.default.capacity yarn.scheduler.capacity.root.accessible-node-labels.default.maximum-capacity ... View more

If you have imported and started the sandbox you should be able to access Ambari via sandbox.hortonworks.com:8080 or 127.0.0.1:8080. You can access the sandbox via shell by using Putty (Windows) and the following command: ssh root@sandbox.hortonworks.com -p 2222 Additional information about the installation are available in our Sandbox docs: http://hortonworks.com/wp-content/uploads/2015/07/... ... View more

@yan Adiputra Just looking at your logs, looks like the problem is a wrong memory configuration: 2015-12-10 09:57:39,443 INFO service.AbstractService (AbstractService.java:noteFailure(272)) - Service RMActiveServices failed in state INITED; cause: org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Invalid resource scheduler memory allocation configuration, yarn.scheduler.minimum-allocation-mb=3072, yarn.scheduler.maximum-allocation-mb=2250, min and max should be greater than 0, max should be no smaller than min. org.apache.hadoop.yarn.exceptions.YarnRuntimeException: Invalid resource scheduler memory allocation configuration, yarn.scheduler.minimum-allocation-mb=3072, yarn.scheduler.maximum-allocation-mb=2250, min and max should be greater than 0, max should be no smaller than min. at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.validateConf(CapacityScheduler.java:179) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.initScheduler(CapacityScheduler.java:308) at org.apache.hadoop.yarn.server.resourcemanager.scheduler.capacity.CapacityScheduler.serviceInit(CapacityScheduler.java:348) at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) at org.apache.hadoop.service.CompositeService.serviceInit(CompositeService.java:107) at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager$RMActiveServices.serviceInit(ResourceManager.java:572) at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.createAndInitActiveServices(ResourceManager.java:972) at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.serviceInit(ResourceManager.java:259) at org.apache.hadoop.service.AbstractService.init(AbstractService.java:163) at org.apache.hadoop.yarn.server.resourcemanager.ResourceManager.main(ResourceManager.java:1202) According to the logs the following config is set: yarn.scheduler.maximum-allocation-mb=2250 yarn.scheduler.minimum-allocation-mb=3072 This config is impossible min has to be smaller than max Could you please switch the configurations, so that you have: yarn.scheduler.maximum-allocation-mb=3072 yarn.scheduler.minimum-allocation-mb=2250 ... View more