Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The requirements are governed by two sources: CDAP and YARN, and the requirements are described here.

How do I set the CDAP properties for components running on multiple machines?

...

If you've installed the cdap-cli RPM or DEB, it's located under /opt/cdap/cli/bin. If you have installed CDAP manually (without using Cloudera Manager or Apache Ambari), you can add this location to your PATH to prevent the need for specifying the entire script every time.

Note: These commands will list the contents of the package cdap-cli, once it has been installed:

Code Block
$ rpm -ql cdap-cli
$ dpkg -L cdap-cli

...

I've followed the install instructions, yet CDAP does not start. What next?

If you have followed the installation instructions, and CDAP either did not startup, check:

  • Look in the CDAP logs for error messages (located either in /var/log/cdap for Distributed CDAP or $CDAP_HOME/logs for CDAP Sandbox)

  • If you see an error such as:

    Code Block
    ERROR [main:c.c.c.StandaloneMain@268] - Failed to start CDAP Sandbox
    java.lang.NoSuchMethodError:
    io.cdap.cdap.UserInterfaceService.getServiceName()Ljava/lang/String
    

    then you have downloaded the CDAP Sandbox version of CDAP, which is not intended to be run on Hadoop clusters. Download the appropriate distributed packages (RPM or Debian version) from http://cdap.io/get-started/downloads.

  • Check permissions of directories:

    • The CDAP HDFS User (by default, yarn) owns the HDFS directory (by default, /cdap).

    • The Kafka Log directory (by default, /data/cdap/kafka-logs), must be writable by the CDAP UNIX user.

    • The temp directories utilized by CDAP must be writable by the CDAP UNIX user.

...

  1. Check if the JDK being used is supported by CDAP:

    Code Block
    $ java -version
    
  2. Check if the CDAP user is using a correct version of the JDK:

    Code Block
    $ sudo su - <cdap-user>
    $ java -version
    
  3. Run this command to see if all the CDAP classpaths are included:

    Code Block
    $ /opt/cdap/master/bin/cdap classpath | tr ':' '\n'
    

    Expect to see (where <version> is the appropriate hbase-compat version):

    Code Block
    /etc/cdap/conf/
    /opt/cdap/hbase-compat-<version>/lib/*
    /opt/cdap/master/conf/
    /opt/cdap/master/lib/*
    

    If the classpath is incorrect (in general, the hbase-compat-<version>/lib/* and cdap/master/lib/* entries must precede any other paths that contain JARs or classes such as the HBase classpath), review the installation instructions and correct.

We aren't seeing any Metrics or Logs. What should we do?

...

In general, no. (The exception is an upgrade from 2.8.x to 3.0.x.) This table lists the upgrade paths available for different CDAP versions:

Version

Upgrade Directly To

3.2.x

3.3.x

3.1.x

3.2.x

3.0.x

3.1.x

2.8.x

3.0.x

2.6.3

2.8.2

If you are doing a new installation, we recommend using the current version of CDAP.

...