Last modified: 2014-08-14 17:54:41 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T71463, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 69463 - Create a table in labs with replication lag data
Create a table in labs with replication lag data
Status: NEW
Product: Analytics
Classification: Unclassified
General/Unknown (Other open bugs)
unspecified
All All
: Unprioritized enhancement
: ---
Assigned To: Sean Pringle
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2014-08-13 10:24 UTC by nuria
Modified: 2014-08-14 17:54 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description nuria 2014-08-13 10:24:14 UTC 
I am creating this bug at the request of springle.

It will be very useful to be able to consult replication lag on a table with wide access. 

The analytics team has nightly reports that compute stats for the day. If replication lag is too high there might not be any data for that day, thus teh report will look "artifically" empty. 

We could monitor timestamps of data but it will be much more useful to have a table we could consult with replication lag data before our daily run, if the lag is too high the run will just not happen. Our software backfills so if today's run is skipped we will log the issue and tomorrow's run can backfills today data if issue is resolved.
Comment 1 nuria 2014-08-13 10:35:12 UTC 
We schedule reports by project and i imagine replication will reported per host, not per project so a global measure of how replication is working on the labs cluster will be sufficient for us.
Comment 2 nuria 2014-08-13 14:37:42 UTC 
Please note that this table needs to exist on the labs side, not on the production side.
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links