I'm pretty sure the PER_CONTAINER statement works as follows for a each instantiation of a particular service within a slider app: 1) check the allowable port range 2) look for an available port on the machine within the allowed port range 3) launch with selected port
In the case of Accumulo, if you're running two tservers on the same box and have a range of ports that they can use, they will not conflict. However, if you statically set the tserver's port and two launch on the same machine, they will both try to use it and conflict. One will eventually relaunch on a node with an available port provided resources exist and you don't exceed your failure threshold. If you are having an issue with your app master not launching, it might be because you specified a port or port range that is fully utilized by another application on the same box. Is your cluster idle or do you have other slider apps running? Do you have more complete output of the logs and possibly the appConfig that you can share? Are you sure it's the AM failing to start and not a service within your slider app? Tim On May 16, 2016 4:02 PM, "Manoj Samel" <[email protected]> wrote: Hello, When using ALLOCATED_PORT clause, there is a option "PER_CONTAINER". Can someone explain what does "PER_CONTAINER" option does ? It says keep port allocation private to container. What does that means ? If multiple containers are chosen to on same host machine, will this cause issue ? When using a specific port range using site.global.slider.allowed.ports, I am getting frequent errors in starting slider AM. The log says *2016-05-14 20:39:29,236 [main] ERROR main.ServiceLauncher - No available ports found in configured range {}* 2016-05-14 20:39:29,237 [main] INFO util.ExitUtil - Exiting with status 77 The error is not hard, sometimes same port range works file. I am wondering if this has anything to do with PER_CONTAINER ... This is on slider 0.80 on Hadoop 2.6 secured cluster ... Than
