Closed Bug 1121403 Opened 10 years ago Closed 10 years ago

Redis error: WRONGTYPE Operation against a key holding the wrong kind of value

Categories

(Hello (Loop) :: Server, defect)

x86_64
Linux
defect
Not set
blocker

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: alexis+bugs, Assigned: alexis+bugs)

References

Details

Attachments

(1 file)

56 bytes, text/x-github-pull-request
leplatrem
: review+
Details | Review
This is probably due to the fact we changed how data is handled for room participants. We were previously using hashes and now are using sets, in order to expire them properly. This change was introduced with bug 1093569. We haven't detected that on staging due to how we're doing the verification (I think), but on dev. The sentry ticket is for the dev instance, but doesn't really point to which key was holding the wrong value. https://app.getsentry.com/mozilla/loop/group/50469413/
Assignee: nobody → alexis+bugs
I've been able to reproduce this and it's effectively pre-empting a call to work if it started on 0.14.3 and someone tries to join the conversation using 0.15.0. We'll solve this with a migration script, to copy over the keys from the old format to the new format. This script should be run just when the new server will be targeted.
Blocks: 1120911
Attached file link to github PR
Attachment #8549245 - Flags: review?(mathieu)
Attachment #8549245 - Flags: review?(mathieu) → review+
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: