3 ms·

Apparently now fixed: "20 Jun 2024 22:06 PDT We identified and fixed the issue with indexing. Sites may still experience some delayed indexing until the previ

by tyingq 2y ago

Apparently now fixed: "20 Jun 2024 22:06 PDT We identified and fixed the issue with indexing. Sites may still experience some delayed indexing until the previously affected URLs have been reprocessed. There will be no more updates." https://status.search.google.com/incidents/Gjz5TP3aaDRmKsSWgWF4 https://status.search.google.com/incidents/Gjz5TP3aaDRmKsSWg...

beardyw 2y ago
6 minutes earlier" "Google is investigating reports about delayed indexing in Google Search. We're working on identifying the root cause. Next update will be within 12 hours." I doubt they did it in 6 minutes!
- viraptor 2y ago
  It's possible, if it was some silly omission. Also, it takes a few minutes before a status like that is posted in the first place. (Possibly different teams)
  - fifticon 2y ago
    [flagged]
    - viraptor 2y ago
      What does that have in common with the topic?
      - RIMR 2y ago
        Nothing, just another person who absolutely has to bring up some sort of unrelated politics in every conversation. If it's not Russia/Ukraine, it's Israel/Palestine, and while those topics are important, I wish people would back off and stop injecting these topics into everything else.
- nostrademons 2y ago
  There's a delay as information makes its way from engineering to external comms. Very likely, the indexing issue happened late in the afternoon after the comms person had gone home for the day (the tweet is 4:00 PM), a situation room was convened with a bunch of SREs and engineers with expertise, they sent an e-mail to external comms saying "Post that we're having issues with indexing", they got to work diagnosing the problem, they pushed a fix in a couple hours, and then they sent another e-mail saying "The issue is fixed." The external comms person checks their phone after the kids have gone to bed, sees an urgent message about an indexing failure, posts that on the status blog, then checks the rest of their e-mail and sees that it's resolved, so they post that.
  - thiagocsf 2y ago
    Plausible but likely wrong. A dedicated comms person is part of the incident response team. https://sre.google/sre-book/managing-incidents/ https://sre.google/sre-book/managing-incidents/

by tyingq 2y ago

beardyw 2y ago

6 minutes earlier" "Google is investigating reports about delayed indexing in Google Search. We're working on identifying the root cause. Next update will be within 12 hours." I doubt they did it in 6 minutes!

viraptor 2y ago
It's possible, if it was some silly omission. Also, it takes a few minutes before a status like that is posted in the first place. (Possibly different teams)
- fifticon 2y ago
  [flagged]
  - viraptor 2y ago
    What does that have in common with the topic?
    - RIMR 2y ago
      Nothing, just another person who absolutely has to bring up some sort of unrelated politics in every conversation. If it's not Russia/Ukraine, it's Israel/Palestine, and while those topics are important, I wish people would back off and stop injecting these topics into everything else.
nostrademons 2y ago
There's a delay as information makes its way from engineering to external comms. Very likely, the indexing issue happened late in the afternoon after the comms person had gone home for the day (the tweet is 4:00 PM), a situation room was convened with a bunch of SREs and engineers with expertise, they sent an e-mail to external comms saying "Post that we're having issues with indexing", they got to work diagnosing the problem, they pushed a fix in a couple hours, and then they sent another e-mail saying "The issue is fixed." The external comms person checks their phone after the kids have gone to bed, sees an urgent message about an indexing failure, posts that on the status blog, then checks the rest of their e-mail and sees that it's resolved, so they post that.
- thiagocsf 2y ago
  Plausible but likely wrong. A dedicated comms person is part of the incident response team. https://sre.google/sre-book/managing-incidents/ https://sre.google/sre-book/managing-incidents/