[DOC] Cannot navigate to any docs pages, keep redirecting to docs front page

[drewmiranda-gl]

This is the second time this has happened. Is this normal/expected?

[kkhatua]

This looks to be a duplicate of https://github.com/opensearch-project/documentation-website/issues/6586

[drewmiranda-gl]

Doing a quick bit of troubleshooting, I was originally trying to reach https://opensearch.org/docs/latest/monitoring-your-cluster/pa/index/ which would just either redirect to https://opensearch.org/docs or show the error in the screenshot above.

It appears i can simulate this behavior by navigating to an invalid docs page, such as https://opensearch.org/docs/latest/monitoring-your-cluster/pa/index/d

Curl shows the following:

< HTTP/2 302 
< content-type: application/xml
< content-length: 0
< date: Tue, 10 Dec 2024 17:55:41 GMT
< server: AmazonS3
< location: /docs/latest/

This could be purely coincidental but the timing seems to overlap with the most recent PR https://github.com/opensearch-project/documentation-website/pull/8920

I'm not sure what the build process is like but is it possible there is a weird condition where the docs site is missing paths during the build and those missing paths get redirected?

Edit to add: Interesting, this appears to be a known issue already: https://github.com/opensearch-project/documentation-website/issues/5846#issuecomment-1854508146

[Naarcha-AWS]

@drewmiranda-gl: We've noticed that when pushing multiple PRs at a time to production that more people experience the redirect issue. We're currently discussing pushing PRs during non-peak hours to help mitigate this issue.

[dblock]

[Catch All Triage - 1, 2, 3, 4, 5, 6]

[dblock]

@drewmiranda-gl: We've noticed that when pushing multiple PRs at a time to production that more people experience the redirect issue. We're currently discussing pushing PRs during non-peak hours to help mitigate this issue.

The update should be incremental/in-place. The current behavior causes Google to briefly hit pages that return 404 and is destructive for SEO.

[natebower]

@kolchfa-aws

[smacrakis]

"...and is destructive for SEO."

Not being able to serve static content reliably makes us look like amateurs.