You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Background

Hive build jobs include Hive PreCommit Testing, and scheduled builds of various branches with various flags.  They are run on the Hive Ptest2 Infrastructure, which is a EC2 cluster currently sponsored by Cloudera, which runs each build sequentially, but splits the testing across all the resources of the cluster to achieve much higher throughput.

Location

The infrastructure master is at ec2-174-129-184-35.compute-1.amazonaws.com.  Committers can be granted access to this host by request, see HIVE-4739.

Processes

The infrastructure master hosts two processes:

  1. Jenkins: http://ec2-174-129-184-35.compute-1.amazonaws.com/jenkins/
    • This is the admin for Hive builds.  In the dashboard, user can see state of build queue, test results of past builds, etc.  
    • Builds are submitted either manually in the dashboard UI, automatically by patch upload (See Hive PreCommit Testing), or by schedule (branch builds).
  2. Hive PTest WebServer
    • Exposes a REST API to take test request from the Jenkins builds.  Each request specifies a profile property-file, which contains a set of properties such as what branch to build, what tests to run.
    • On a test request:
      • Creates EC2 slaves, which are spot-instances.
      • Reads the specified property-file and compiles source code using it.
      • Distributes the compiled code across the EC2 slaves, makes SSH calls to run the tests remotely in parallel, and gather the results.
      • If no further test request come in 30 minutes, the slaves are shutdown.

Jenkins Configuration/Debug

  • Jenkins logs:  /var/log/jenkins/jenkins.log
  • Jenkins config: /etc/sysconfig/jenkins
  • Jenkins home: /var/lib/jenkins  (job info is located at /var/lib/jenkins/jobs)

Hive PTest Configuration/Debug

FAQ:

How do I restart Jenkins?

sudo service jenkins restart

How do I setup a new branch build?

In /usr/local/hiveptest/public/ you can copy existing profile property-file, and update the branch property.  Then in Jenkins, copy an existing branch build, and in the build config modify the profile argument in the Hive Ptest2 Webserver call to point to the new profile.

How can I read or make changes to Hive PTest Infra code?

Code is located in hive git repo.  It is under /hive/testutils/ptest2.  As the Hive Ptest2 Webserver is a running process, if changes are made, it needs to be restarted.

How do I stop, start, restart the Hive PTest2 server, or have it use the latest test infra code?

$ sudo /usr/local/hiveptest/bin/stop-server.sh 
$ sudo /usr/local/hiveptest/bin/start-server.sh 
$ sudo /usr/local/hiveptest/bin/restart-server.sh 
$ sudo /usr/local/hiveptest/bin/update.sh
  • No labels