Closed Bug 512513 Opened 10 years ago Closed 10 years ago

Some forum posts / replies take over 20 minutes to show


( :: Forum, task)

Not set


(Not tracked)



(Reporter: TMZ, Assigned: jsocol)


Some forum replies take over 20 minutes from when they were submitted to actually showing on the forum. I have seen this myself and recently it has been reported in #sumo. On some occasions it may be the cache as adding junk such as "&test=123" to the end of the URL fixes it, other times you just have to sit and wait it out. 

This also happens on others posts such as you get the reply email including the post but when you visit the thread it is not shown.
IT issue?
CCing Laura
Dupe of bug 512841?
Might be related, but it doesn't sound like a dupe?
Jame clarified on bug 512841 that it isn't a dupe. I'll nominate this for 1.4.2 then.
Target Milestone: --- → 1.4.2
To have it in both places: This looks to me like a replication lag issue.

Does it ever occur on stage?
CCing IT for some insight here.

Shyam or Derek, do you have any advice for deciding if this is replication lag and, if it is, any advice for fixing it?
Assignee: nobody → james
No ideas yet -> 1.5
Target Milestone: 1.4.2 → 1.5
Target Milestone: 1.5 → 1.5.1
On the replication lag issue - next time this is noticed, tmz, try to ping us in IRC and we can check if lag is present at that time.  It does sound like lag to me, and we've seen this issue before (cilias will remember).  We might also be able to work around it using force_master for posters.  I think right now that gets used for 60 seconds after posting.

Of course if we have a 10 minute lag we have a bigger problem to solve...
Target Milestone: 1.5.1 → 1.6
I haven't seen this for a while now. I will keep my eyes open.
Has anyone noticed this lately? If not, can we close this bug?
(In reply to comment #11)
> Has anyone noticed this lately? If not, can we close this bug?

If anyone sees this, please reopen.
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.