I haven't run the functional suite myself for this RC. I seem to recall
having run the tests on a single VM at some point in the past. Maybe the VM
needs to have enough resources to run all the containers requested, though?
On Sun, Mar 12, 2017 at 7:05 PM, jonma...@gmail.com
wrote:
> Having trou
Please provide some additional info -
1. Can you login to the AM container node and look under the container log
dir and see if the logs files are there?
2. If you don¹t see the log files in step 1 above, can you run the below
yarn cmd-line? Do you see the logs?
yarn logs -applicationId
3. If
Jon,
Thank you for looking into the RC.
I successfully ran the FTs against a HDP 2.4.x cluster. My cluster is a
multi-node cluster but I don¹t think it has to be one (except if you want
to run AppsThroughAgentQueueAndLabelsIT which needs a multi-node cluster
with multiple labels). However as Billi
1. the AM container has an empty log dir. The timestamp on the dir is the time
when the job was launched.
The app container (on a different node) has some files in the log dir
(command*json, errors*txt, output*txt, status_command*, slider-agent*).
Nothing helpful.
2. that command throws an er
Sorry my bad. It is yarn.nodemanager.log.retain-seconds. Copy paste error.
2. You see that error because the version of hadoop you have does not show logs
of a running app.
3. Are there any other apps which are in stopped state already? If yes, then
can you run the yarn logs cmd on it?
-Gour
I'm confused by the documentation for instance counts.
resources.json specifes the number of instances of a component, but metainfo
specifies min and max.
How do these two configurations interact? If I want to start my app with N
instances of a component, but want to be able to flex to N+M insta
Thanks! I suspected environmental issues, and thought that disabling both
vmem and pmem checks might suffice, but they did not. I may explore some
more to ascertain the reasons my failures (as an educational exercise ;) )
I had success with other validations:
- signatures and checksums
- builds
minInstanceCount and maxInstanceCount in metainfo is used to define the
absolute range of the no of running instances for a specific component of
your application. It depends a lot on your application logic. For e.g. If
your app has a master and there cannot be more than 1 running master at a
given
