-
Notifications
You must be signed in to change notification settings - Fork 3.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
kvserver: v22.2.3: nil pointer in (quotapool.RateLimiter).WaitN #96231
Comments
cockroach-teamcity
added
C-bug
Code not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.
O-sentry
Originated from an in-the-wild panic report.
labels
Jan 30, 2023
We are also saw this issue once in our CI with v22.2.3 :
|
yuzefovich
changed the title
sentry: panic.go:965: runtime error: invalid memory address or nil pointer dereference
--
runtime.errorString
panic.go:965: *withstack.withStack (top exception)
storage: v22.2.3: nil pointer in computeStatsForIterWithVisitors
Feb 23, 2023
jbowens
changed the title
storage: v22.2.3: nil pointer in computeStatsForIterWithVisitors
kvserver: v22.2.3: nil pointer in (quotapool.RateLimiter).WaitN
Mar 1, 2023
Looks like the quota pool backing the rate limiter is nil? Appears to be above storage. |
craig bot
pushed a commit
that referenced
this issue
Apr 4, 2023
100539: sql: add telemetry for UDFs with RETURNS TABLE r=mgartner a=mgartner Informs #100226 Release note: None 100554: kv: initialize consistencyLimiter during Store construction, before Start r=aliher1911 a=nvanbenschoten Fixes #96231. This commit attempts to fix #96231. It moves the initialization of `Store.consistencyLimiter` up from the bottom of `Store.Start` into `NewStore`. It is unsafe to initialize this variable after the call to `Store.processRaft`, which starts Raft processing. Beyond that point, incoming Raft traffic is permitted and calls to `computeChecksumPostApply` are possible. The two stacktraces we have in that issue conclusively point to the `Store.consistencyLimiter` being nil during a call to `(*Replica).computeChecksumPostApply`. This startup-time race is the only possible explanation I could come up with. Release note (bug fix): Fixed a rare startup race that could cause an `invalid memory address or nil pointer dereference` error. 100592: storage: remove unnecessary version override in unit test r=nicktrav a=jbowens Remove an unnecessary use of cluster.MakeTestingClusterSettingsWithVersions in favor of cluster.MakeTestingClusterSettings. Epic: None Informs: #100552 Release note: None Co-authored-by: Marcus Gartner <[email protected]> Co-authored-by: Nathan VanBenschoten <[email protected]> Co-authored-by: Jackson Owens <[email protected]>
blathers-crl bot
pushed a commit
that referenced
this issue
Apr 4, 2023
…tart Fixes #96231. This commit attempts to fix #96231. It moves the initialization of `Store.consistencyLimiter` up from the bottom of `Store.Start` into `NewStore`. It is unsafe to initialize this variable after the call to `Store.processRaft`, which starts Raft processing. Beyond that point, incoming Raft traffic is permitted and calls to `computeChecksumPostApply` are possible. The two stacktraces we have in that issue conclusively point to the `Store.consistencyLimiter` being nil during a call to `(*Replica).computeChecksumPostApply`. This startup-time race is the only possible explanation I could come up with. Release note (bug fix): Fixed a rare startup race that could cause a `invalid memory address or nil pointer dereference` error.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This issue was autofiled by Sentry. It represents a crash or reported error on a live cluster with telemetry enabled.
Sentry link: https://sentry.io/organizations/cockroach-labs/issues/3906561739/?referrer=webhooks_plugin
Panic message:
Stacktrace (expand for inline code snippets):
/usr/local/go/src/runtime/panic.go#L964-L966 in runtime.gopanic
/usr/local/go/src/runtime/panic.go#L211-L213 in runtime.panicmem
/usr/local/go/src/runtime/signal_unix.go#L733-L735 in runtime.sigpanic
cockroach/pkg/util/quotapool/int_rate.go
Lines 58 to 60 in af7f257
cockroach/pkg/kv/kvserver/replica_consistency.go
Lines 580 to 582 in af7f257
cockroach/pkg/storage/mvcc.go
Lines 3985 to 3987 in af7f257
cockroach/pkg/kv/kvserver/replica_consistency.go
Lines 635 to 637 in af7f257
cockroach/pkg/kv/kvserver/replica_proposal.go
Lines 243 to 245 in af7f257
cockroach/pkg/kv/kvserver/replica_proposal.go
Lines 249 to 251 in af7f257
cockroach/pkg/util/stop/stopper.go
Lines 441 to 443 in af7f257
/usr/local/go/src/runtime/asm_amd64.s#L1370-L1372 in runtime.goexit
v21.2.2
Jira issue: CRDB-24018
The text was updated successfully, but these errors were encountered: