A small rerate (last 2-3 months) is scheduled to run overnight, and we will probably continue to run small rerates like that overnight on a daily basis to see if that reduces reports of sequencing issues.
1 Like
Is the rerate complete? I ask because the problem which I mentioned in the other post has not been resolved
I don’t know and a few issues I was tracking don’t seem to have gotten fixed yet either, so either it’s not done or there still an issue.
It’s still an issue. This player is just one of the many examples: US Chess. I can provide a number of other examples from this tournament US Chess
I don’t think the rerate ran, but I haven’t heard directly on that issue.
Do we know when/if a rerate is expected
I haven’t heard anything on this yet, and I’ve sent another request for an update on the rerate status.
There is a rerate scheduled for 2AM, but there was an issue with the last one so this one has more logging to try to find out where the problem is, which means it may not complete–again.
Once we get past this issue, there will be a short rerate run every night, which should take care of recently submitted events that are out of time sync. A longer rerate will continue to be run weekly, probably on Tuesdays, to deal with corrections to previously rated events.
I hope it works. Because the issues are still there
Well, the event I was tracking is flowing properly now, looks like it is still running, it’s up to about November 10th.
HI all this looks like good news. I submitted an issue to ratingsmgr@uschess.org about a recently submitted event that had a posting error. I know these kinds of things may not be highest priority, but do you know if these may be addressed soon? Appreciated.
John D
Korey is making corrections, I don’t know what his backlog is. Once a correction is made it should be rated again, so you’ll see the impact of the corrections, but it’ll take another rerate to get the corrected ratings flowing from one event to the next.
If it’s within the window for overnight rerates (2+ months) it should pick it up overnight, but any from before October won’t be picked up until we run a larger rerate, hopefully next week.
The event in question was November 24. Not resolved yet
The event in question is still unresolved
Yeah, the event it blew up on was a Nov 21st event. Not sure exactly why it’s failing, but some query optimization is likely the next step. (I spent a lot of time tuning the original rerate program, too.)
The difference between between being the developer and just a liaison to them is that I don’t get inside stuff like this, which is where DBMs like me love to be. (I got the program I wrote to the point where it was rating about 6 events a second.)
So what is the next course of action
I know they’ve been working on some query optimization, but I’m not familiar with the monitoring and tuning tools available in SQL Server.
Is the relate holding up other events ? The tournament I submitted around 10 last night is still in the queue. ID #202512120153.
My issue is finally fixed!!
Yes, it looks like the query improvements worked and the rerate is finished.
They suspended rating new events during the rerate, now they need to turn that back on.