Last modified: 2014-08-04 14:38:56 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 T68911, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 66911 - Make wikimetrics use standard Redis configuration again
Make wikimetrics use standard Redis configuration again
Status: RESOLVED FIXED
Product: Analytics
Classification: Unclassified
Wikimetrics (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-06-21 09:50 UTC by christian
Modified: 2014-08-04 14:38 UTC (History)
7 users (show)

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


Attachments

Description christian 2014-06-21 09:50:20 UTC
Wikimetrics started to use a custom redis configuration [1] to
overcome persistence issues. The point was made [2] that this custom
configuration was not needed.

So if it's possible, let's switch back to redis' default configuration.



[1] https://git.wikimedia.org/commit/operations%2Fpuppet.git/05220a35917f64d43288cc1c891d89cd5f078dfb

[2] During code-review of an unrelated change; see line 193 of
  https://gerrit.wikimedia.org/r/#/c/139558/6/manifests/role/wikimetrics.pp
Comment 1 Gerrit Notification Bot 2014-06-21 09:54:50 UTC
Change 141116 had a related patch set uploaded by QChris:
Parametrize redis' dbfilename

https://gerrit.wikimedia.org/r/141116
Comment 2 Gerrit Notification Bot 2014-06-21 10:40:04 UTC
Change 141120 had a related patch set uploaded by QChris:
Have Wikimetrics use the redis module's configuration again

https://gerrit.wikimedia.org/r/141120
Comment 3 Dan Andreescu 2014-06-22 20:37:19 UTC
I disagree, the custom configuration for redis solves other persistence issues.  The settings in our custom configuration ensure that Wikimetrics saves more often, which is useful in case of crashes.  It also ensures that it fails loudly when writing to file is not possible, which happened in the past and caused a lot of data loss because redis failed silently.
Comment 4 nuria 2014-06-23 08:30:55 UTC
I think that having our own config is useful too. On the CR I was just making the point that TTLs for persistence of celery reports in redis are actually handled via celery, not redis (we just realized this recently)
Comment 5 christian 2014-06-23 08:59:21 UTC
(In reply to Dan Andreescu from comment #3)
> the custom configuration for redis solves other persistence
> issues.

Yup. That's why I explicitly called them out on change 141120's
commit message :-)

As it now seems we want to keep them, and since they differ by only
two settings, I'll try adding knobs for them in wmf's redis module.
That way, we can use our custom settings, and still get the benefit
of Ops maintaining the redis module.
Comment 6 nuria 2014-06-23 13:39:23 UTC
If that can be done that would be the best solution, christian.
Comment 7 Gerrit Notification Bot 2014-06-24 14:14:48 UTC
Change 141116 merged by Ottomata:
Parametrize redis' settings needed for Wikimetrics

https://gerrit.wikimedia.org/r/141116
Comment 8 Gerrit Notification Bot 2014-06-25 10:14:52 UTC
Change 141918 had a related patch set uploaded by QChris:
Take advantage of redis module again

https://gerrit.wikimedia.org/r/141918
Comment 9 Gerrit Notification Bot 2014-06-25 20:50:23 UTC
Change 141918 abandoned by QChris:
Take advantage of redis module again

Reason:
Doing it in Idecc81b2e052ed5d777a321141f60336ba8ae26b only.

https://gerrit.wikimedia.org/r/141918
Comment 10 Gerrit Notification Bot 2014-06-27 14:14:16 UTC
Change 141120 merged by Ottomata:
Have Wikimetrics use the redis module's configuration again

https://gerrit.wikimedia.org/r/141120

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links