Verification

To verify that the CDAP software is successfully installed and you are able to use your Hadoop cluster, run an example application. We provide in our SDK pre-built JAR files for convenience.

  1. Download and install the latest CDAP Software Development Kit (SDK).
  2. Extract to a folder (CDAP_HOME).
  3. Open a command prompt and navigate to CDAP_HOME/examples.
  4. Each example folder has a .jar file in its target directory. For verification, we will use the WordCount example.
  5. Open a web browser to the CDAP UI. It is located on port 9999 of the box where you installed the CDAP UI service.
  6. On the UI, click the button Add App.
  7. Find the pre-built WordCount-3.4.3.jar using the dialog box to navigate to CDAP_HOME/examples/WordCount/target/.
  8. Once the application is deployed, instructions on running the example can be found at the WordCount example.
  9. You should be able to start the application, inject sentences, and retrieve results.
  10. When finished, you can stop and remove the application as described in the section on Building and Running CDAP Applications.

Getting a Health Check

Administrators can check the health of various services in the system. (In these examples, substitute for <host> the host name or IP address of the CDAP server.)

  • To retrieve the health check of the CDAP UI, make a GET request to the URI:

    http://<host>:9999/status
    
  • To retrieve the health check of the CDAP Router, make a GET request to the URI:

    http://<host>:10000/status
    
  • To retrieve the health check of the CDAP Authentication Server, make a GET request to the URI:

    http://<host>:10009/status
    

On success, the calls return a valid HTTP response with a 200 code.

  • To retrieve the health check of all the services running in YARN, make a GET request to the URI:

    http://<host>:10000/v3/system/services
    

    On success, the call returns a JSON string with component names and their corresponding statuses (reformatted to fit):

    [{"name":"appfabric","description":"Service for managing application
      lifecycle.","status":"OK","logs":"OK","min":1,"max":1,"requested":1,"provisioned":1},
     {"name":"dataset.executor","description":"Service to perform dataset
      operations.","status":"OK","logs":"OK","min":1,"max":1,"requested":1,"provisioned":1},
     {"name":"explore.service","description":"Service to run ad-hoc
      queries.","status":"OK","logs":"OK","min":1,"max":1,"requested":1,"provisioned":1},
     {"name":"log.saver","description":"Service to collect and store
      logs.","status":"OK","logs":"NOTOK","min":1,"max":1,"requested":1,"provisioned":1},
     {"name":"metrics","description":"Service to handle metrics
      requests.","status":"OK","logs":"OK","min":1,"max":1,"requested":1,"provisioned":1},
     {"name":"metrics.processor","description":"Service to process application and system
      metrics.","status":"OK","logs":"NOTOK","min":1,"max":1,"requested":1,"provisioned":1},
     {"name":"streams","description":"Service that handles stream data
      ingestion.","status":"OK","logs":"OK","min":1,"max":1,"requested":1,"provisioned":1},
     {"name":"transaction","description":"Service that maintains transaction
      states.","status":"OK","logs":"NOTOK","min":1,"max":1,"requested":1,"provisioned":1}]