Daniel Weeks

The limit is here: https://github.com/Netflix/inviso/blob/master/web-ui/public/js/cluster.js#L192 The purpose of the limit is to ensure that the results can be retrieved in a reasonable amount of time and D3 can render it....

What version of hadoop are you running against?

Took another look and it's probably trying to used the wrong port to talk to the name node (it defaults to 9000 which is what EMR uses). Try adding the...

The default ports are based on EMR, which is not the hadoop default. Just change the ports in those scripts to whatever you're running your RM on.

So, that means the the job history isn't loading properly and just the job config information is available. You can check the logs from the tomcat server (catalina.out and inviso.log)...

It looks like you're running tomcat as root instead of as hadoop ``` user=root, access=EXECUTE, inode="/tmp":hadoop:supergroup:drwx------ ``` You can either run tomcat as hadoop or update your `tomcat/bin/setenv.sh` to export...

It looks like the same port issue most people are having. The default port used by inviso is the port used by EMR. Take a look at the ports used...

Hmm, can you make sure you the NN is listening on localhost? Try a 'telnet localhost 8020'. Otherwise specify host or ip in settings.py. From the trace, I can't tell...

@Slouis61 I just pulled down the HDP 2.2 Sandbox and was able to get it all running with the following mods: jes.py ``` --- a/jes/jes.py +++ b/jes/jes.py @@ -27,6 +27,7...

Currently only supports MR Jobs, but could be extended to support just about anything that has sufficient detail for job history. The Timeline Server can probably provide this info in...