Fixed
Pinned fields
Click on the next to a field label to start pinning.
Details
Assignee
Kevin CherkauerKevin Cherkauer(Deactivated)Reporter
Jeelan PoolaJeelan Poola(Deactivated)Is this a Regression?
UnknownTriage
UntriagedStory Points
1Priority
CriticalInstabug
Open Instabug
Details
Details
Assignee
Kevin Cherkauer
Kevin Cherkauer(Deactivated)Reporter
Jeelan Poola
Jeelan Poola(Deactivated)Is this a Regression?
Unknown
Triage
Untriaged
Story Points
1
Priority
Instabug
Open Instabug
PagerDuty
PagerDuty
PagerDuty
Sentry
Sentry
Sentry
Zendesk Support
Zendesk Support
Zendesk Support
Created August 5, 2021 at 10:35 AM
Updated August 19, 2021 at 5:10 AM
Resolved August 5, 2021 at 5:15 PM
secondary/indexer/storage_manager.go handleIndexMergeSnapshot() does not lock, and its caller does not hold, the s.muSnap mutex (apparently it used to lock this at the top), but it still contains rarely-entered error reporting code blocks that unlock this mutex. If one of these error blocks gets entered, it triggers a panic.
The fix is to delete the s.muSnap.Unlock() calls from this method. There are three of them (one is in commented-out code and two are in live code).
Seen in currently undelivered new version of set14_rebalance_test.go TestFailoverAndRebalance:
http://ci2i-unstable.northscale.in/gsi-04.08.2021-09.40.fail.html