The Cloudera Manager is already capable of tracking usage data via Google Analytics, but that data is beeing send to a cloudera account. This blog post is about configuring the cloudera manager and changing the tracking id so that these usage metrics are being send to your own account.
Our open source project oozie-graphite is now available for CDH5.
Due to some minor incompatibilities between JDK6 and JDK7 the 1.1.0 release of oozie-graphite was not usable on CDH5. The 1.1.0 release of oozie-graphite contains some minor changes to ensure JDK7 compatibility, but no further changes were neccessary use it on Oozie 4.0.0 (CDH5).
This is the first post about GraphiteMRCounterExecutor use cases: we start by utilizing already available hadoop counters that deliver very valueable graphs.
A step-by-step guide on how to install oozie-graphite’s GraphiteMRCounterExecutor.
This blog entry is a step-by-step guide for the GraphiteMRCounterExecutor module installation.
The internal Oozie instrumentation increments counters for various coordinator related actions. Graphing a subset of these counters by utilizing oozie-graphite gives you a good visualisation of your coordinator actions waiting for data to become available and if these dependencies were finally fulfilled or if they did timeout eventually.
The internal Oozie instrumentation keeps track of average execution times for each action type. Graphing a subset of these metrics by utilizing oozie-graphite gives you a good visualisation of your coordinator action performance, especially if you are running custom oozie actions.