After the mobile cache's have been merged into text, we should reorganize the oozie jobs to no longer consider the mobile when starting. If no data comes into the mobile source, these jobs will block until something does.
|operations/puppet : production||eqiad: remove last cache_mobile frontend|
|operations/puppet : production||Remove webrequest_mobile from list of webrequest topics that camus imports|
|analytics/refinery : master||Revert "Revert "Remove mobile webrequest_source merging it in text""|
|analytics/refinery/source : master||Revert "Revert "Use webrequest_source text for AppSessionMetrics, mobile is merging with text""|
|analytics/refinery/source : master||Use webrequest_source text for AppSessionMetrics, mobile is merging with text|
|analytics/refinery : master||Remove mobile webrequest_source merging it in text|
|analytics/refinery : master||Modify oozie job to use jars v0.0.25|
|analytics/refinery/source : master||Clean repo from mobile partition leftovers|
Be aware that after this change we need to document how to proceed for users doing ad hoc selects here:
@JAllemandou, just pushed changes to refinery and refinery-source for removing webrequest_source mobile. Please review :)
Feel free to make changes, merge, and/or build new refinery-source jars and mvn deploy them if you get around to it before I start working in my morning.
Just to be clear: no real user traffic is flowing in webrequest_mobile, but there's still some internal healthcheck traffic keeping the data from dropping off completely. We're blocking now on this oozie change before we can continue with the decom, please fire when ready.
We are mostly done! Our process was here:
We still need to wait for some data to move around in HDFS before we can relaunch a few jobs. But, there are no more running jobs that depend on webrequest_mobile, so @BBlack you can go ahead and start the process of turning off all mobile cache traffic.