Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Yash DodderiYash DodderiReporter
Deepkaran SaloojaDeepkaran SaloojaIs this a Regression?
UnknownStory Points
0Priority
CriticalInstabug
Open Instabug
Details
Details
Assignee
Yash Dodderi
Yash DodderiReporter
Deepkaran Salooja
Deepkaran SaloojaIs this a Regression?
Unknown
Story Points
0
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created November 29, 2022 at 5:12 AM
Updated August 31, 2024 at 11:07 AM
Resolved February 2, 2023 at 3:44 AM
There is a bug during upgrade from 6.6.x to 7.x when transactional ATR/client record documents are present.
1. There was an optimization done in 7.0() to skip ATR/client records in projector and generate UpdateSeqno message in such a case.
projector/worker.go
2. In a mixed mode cluster, projector on 7.0.4 will skip any document with prefix "_txn:"(i.e. ATR/client records or any user created document with prefix "_txn:")
3. The problem is that a 6.6.5 indexer node cannot understand and process an UpdateSeqno message. So these UpdateSeqno messages will get skipped on the indexer node. If these UpdateSeqno messages correspond to SnapEnd of a DCP snapshot marker, indexer will keep waiting indefinitely and lead to index build hang.