Sorry i misses this but it always has sent events to a real high volume.

On Tue, Dec 22, 2015 at 10:25 AM, Jon Katz <jkatz@wikimedia.org> wrote:

+ Dmitry

Hi Nuria,

I will ask Dmitry to confirm, but I think a pause is fine for the next couple of days as long as we are given the timestamps for outage can note it on the schema wiki page.  Is this a sudden increase or has it always been sending to high of a volume?  Regardless, I imagine a higher sampling rate can probably be applied.   

-J

On Tue, Dec 22, 2015 at 9:58 AM, Nuria Ruiz <nuria@wikimedia.org> wrote:

Team:

This  schema MobileWikiAppShareAFact is sending a lot of events, maybe is worth thinking whether we need that many. It is again a case where tables are becoming huge and hard to query fast. 

cc-ing Jon as schema owner.

Can this data be sampled at a higher sampling rate? I have filed a ticket to this fact: 

https://phabricator.wikimedia.org/T122224

Thanks, 

Nuria 

On Tue, Dec 22, 2015 at 8:35 AM, Adam Baso <abaso@wikimedia.org> wrote:

Replacing mobile-tech with mobile-l (internal mobile-tech list discontinued). 

On Tuesday, December 22, 2015, Nuria Ruiz <nuria@wikimedia.org> wrote:

Team:

As part of our effort of converting eventlogging mysql database to the tokudb engine we need to stop eventlogging events from flowing into the MobileWikiAppShareAFact table, we are using this one table to see how long the conversion will take in order to plan for a larger outage window. 

Let us know if data should be backfilled as it can be, we anticipate events will not flow into table for the better part of one day. 

Thanks, 

Nuria

_______________________________________________
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l

_______________________________________________
Analytics mailing list
Analytics@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/analytics