The replicas were falling behind.
I had mentioned it a couple of days earlier. Now I was bringing it up again.
My note to the team was short: take a hard look and, if necessary, work with the developers to find out why we were beginning to see replication lag like this.
“Let's chat first thing this AM.”
Replication lag means the copy is not keeping pace with the database it follows. I do not know how far behind it is yet, which machines are involved, or what is causing it.
I wrote that we were “beginning to see” lag like this. I am not announcing a database failure or a specific customer problem. I am saying the same concern has shown up more than once and now needs a hard look.
I also wrote “if necessary” before bringing in the developers. I do not know that development caused it. First we need the hard look. Then we need the right people based on what that shows.
I do not have a diagnosis. I cannot point to a query, machine, configuration, or change yet. That is why I want the conversation.
Later that day, whether the meeting had actually happened was still an open question. Somebody offered to get the right technical people together if it had not.
The original note came from my iPhone and read like it. “Take a had look.” Capital “Lag” in the middle of a sentence. Short enough that the urgency survived the typos.
The lag is real. The cause is not.