From Wikitech
Jump to navigation Jump to search

Refinery is the software infrastructure that is used on the Analytics Cluster. The source code is in the analytics/refinery repository.

What are we deploying

When deploying new code to the cluster we we might be deploying refinery (just oozie jobs for example) or refinery source (new java code for changes to pageview definition) or both.

  • If you want to deploy refinery source first, follow procedure here: Analytics/Cluster/Refinery-source
  • If we are deploying refinery but no refinery/source then we can just do the scap deploy listed below.
  • If oozie jobs are affected you might need to re-start those.

How to deploy

The refinery now uses Scap so the deployments are as simple as:

  • IMPORTANT: wait about 5 minutes if you just did a refinery-source build. There's a cron that creates the git-fat symlinks and scap will fail if those are missing. And if it does fail, you'll have problems later with the repository on the deploy target (eg. stat1007's /srv/deployment/analytics/refinery will be in an inconsistent state and you'll need to git fat pull or similar)
  • ssh into deployment.eqiad.wmnet
  • First make sure scap config is up to date:
    cd /srv/deployment/analytics/refinery/scap
    git pull
  • Tell the #wikimedia-analytics and #wikimedia-operations IRC channels that you are deploying ( using !log for instance)
  • Create a screen/tmux session to prevent network failures from ruining your deployment.
  • Run:
    cd /srv/deployment/analytics/refinery
    git pull
    scap deploy "Regular analytics weekly train [analytics/refinery@COMMIT_HASH]"
    scap deploy -e thin "Regular analytics weekly train THIN [analytics/refinery@COMMIT_HASH]"

Scap will deploy to the canary host first (stat1007) and then if everything goes fine it will ask you to proceed with the rest of the hosts. If you want to double check the status of the deployment, you can run scap deploy-log and check what is happening. Please note that Scap will create another copy of the repository after each deployment, and it will use symlinks to switch versions.

  • Make sure that all the deployment went fine and rollback in case of fireworks.
  • After the deployment, ssh into an-launcher1002. Make sure to wait until the entire scap deployment is completed before ssh to an-launcher1002. If you cd into the refinery directory before the symlinks change, you'll still be seeing the old git log and be very confused.
  • Change dir into /srv/deployment/analytics/refinery and check (git log) that the code has been pulled.
  • Create a screen/tmux session to prevent network failures to interfere with the execution of the following command.
  • Run sudo -u hdfs kerberos-run-command hdfs /srv/deployment/analytics/refinery/bin/refinery-deploy-to-hdfs --verbose --no-dry-run
    • This part brings the refinery code to the HDFS (but it does not resubmit Oozie jobs, if you need to do so please see the Analytics/Cluster/Oozie/Administration page.)
    • This step can be done on an-launcher1002 (keytab for hdfs is available there).
  • Finally, consider changing any documentation that needs to be updated. This may include: Analytics/Data/Webrequest, Analytics/Data/Pageview_hourly, Research:Page_view (and its sub-pages).

Deploying to labstore* hosts

We deploy refinery to labstore separately from our main deploy targets, avoiding git-fat objects to save disk space. The labstore nodes need the hdfs-rsync script to pull regularly public data from Hadoop. The scap "thin" environment deploys and labstore* hosts right now:

scap deploy -e thin

How to deploy Oozie jobs

You can find test / production deployment information here: Analytics/Cluster/Oozie/Administration

For a tutorial / introduction to oozie, read that page first: Analytics/Cluster/Oozie.