There is a follow up patch to the one mentioned by Sean: 
https://gerrit.wikimedia.org/r/#/c/181204/ 
<https://gerrit.wikimedia.org/r/#/c/181204/>

Since we split up the mobile click tracking schema into multiple schemas we had 
to join tables to get the data needed. However, I think we can look for older 
data in the historic table and only query new data that matches the new schemas.

> On Dec 22, 2014, at 10:57 AM, Nuria Ruiz <[email protected]> wrote:
> 
> Adding mobile tech so they are aware, I am guessing we need to query for that 
> data in a more efficient fashion.
> 
> 
> 
> On Mon, Dec 22, 2014 at 4:10 AM, Sean Pringle <[email protected] 
> <mailto:[email protected]>> wrote:
> Had to kill queries, lest analytics-store grind to a halt and take even 
> longer to recover.
> 
> These ones: https://gerrit.wikimedia.org/r/#/c/178381/ 
> <https://gerrit.wikimedia.org/r/#/c/178381/>
> 
> On Sun, Dec 21, 2014 at 8:09 PM, Sean Pringle <[email protected] 
> <mailto:[email protected]>> wrote:
> This last few days analytics-store replication has started to lag by some 
> hours. Currently s1 (enwiki) and s5 (dewiki, wikidatawiki) are most affected. 
> Eventlogging is not lagging, due to the nicely batched writes it does 
> now-a-days :-)
> 
> There are many slow queries running from the research user on stat1003, 
> referencing eventlogging tables like MobileWebDiffClickTracking*.
> 
> I'm not sure who belongs to them, or if they're new, or if they're safe to 
> kill, so this is mainly a heads-up email. Let us know if ops should kill 
> stuff to let the box catch up again.
> 
> BR
> Sean
> -- 
> DBA @ WMF
> 
> 
> -- 
> DBA @ WMF
> 
> _______________________________________________
> Analytics mailing list
> [email protected] <mailto:[email protected]>
> https://lists.wikimedia.org/mailman/listinfo/analytics 
> <https://lists.wikimedia.org/mailman/listinfo/analytics>
> 
> 

_______________________________________________
Analytics mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/analytics

Reply via email to