Closed Bug 951631 Opened 10 years ago Closed 10 years ago

Investigate problems with db pinning on -dev

Categories

(Marketplace Graveyard :: API, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 951946

People

(Reporter: mat, Unassigned)

Details

I noticed that even when I'm logged in and I just did a POST/DELETE/PATCH/PUT action, the responses of that query and the following ones doesn't say API-Pinning: "True" like it should. And it looks like I'm not pinned at all either. I do see 'api-pinning:<userid>' cache entry set to 1 for 15 seconds, but it doesn't appear to do anything.

In the middleware:
response['API-Pinned'] = str(this_thread_is_pinned())

So if that header is never "True", it probably means pinning doesn't work at all in -dev, somehow. It would explain strange behaviours seen on -dev (possibly prod as well?) from time to time.

Also note, the statsd increments we do are sort of lying: we increment when pin_this_thread() and unpin_this_thread() are called, but we don't check that the request is effectively pinned or unpinned.
Note: this is only on -dev. It'd be also nice to double-check the master-slave configuration on -dev, sometimes I don't see a change on the slave for a minute or more after making it on master, that seems quite long.
I fixed this in bug 951946
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.