-
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
19.2 release blockers list #40447
Comments
We'll need to add Isaac as an Assignee once he's in the system. |
Can we have a tracking issue for this:
|
We never opened an issue for it. It was fixed by #40600. |
Heads up that I have a new horse in the race: #41173 |
I'm adding #41206 to the list. |
added #41222 from andrei pending further assessment |
I added #38720 (comment) from @dt (a node crashed during the |
Added #41415 to the list (changefeed poller bug). |
Added #41694 to the list (bug in table history/poller when fetching old table descriptor versions after a job restart). |
Added #42068 (leases can be transferred to replicas which are being removed) |
Added #42283. |
Long live 19.2 |
Backport patrol
Possible blockers for the 19.2 release:
Build State
KV
BETA BLOCKER storage: non-zero HardState.Commit on uninitialized replica #40213 (Non-zero HardState.Commit on uninitialized replica) @nvanbenschoten
stability: Rebalances must be atomic #12768 (Rebalances must be atomic) @tbg
storage: learner snap can fail when interacting with raft snap #40207 (Learner snap can fail when interacting with raft snap) @danhhz
teamcity: failed test: TestParallel invalid retryable err #40328 (teamcity: failed test: TestParallel invalid retryable err) @nvanbenschoten
roachtest: tpcc/mixed-headroom/n5cpu16 failed #39460 (roachtest: tpcc/mixed-headroom/n5cpu16 failed) @tbg
Slack link (intents ignored when in a read's uncertainty interval, can cause stale reads) @nvanbenschoten
roachtest: acceptance/bank/cluster-recovery failed #38785 (roachtest: acceptance/bank/cluster-recovery failed) @irfansharif
perf: regression since 20190805 release #41206 performance regression (logging memory leak + stats collection inefficiency) @nvanbenschoten
changefeedccl: bug in poller causes it to emit a resolved timestamp before emitting row updates at that timestamp. #41415 bug in poller causes it to emit a resolved timestamp before emitting row updates at that timestamp @aayushshah15. Update: PR for this is in now (changefeedccl: fix bug in poller that allows it to emit a resolved ts before emitting row updates at the ts #41665). Pending backport.
changefeedccl: bug in table history wrt fetching old table descriptor versions after a restart #41694 bug in table history/poller when fetching old table descriptor versions after a restart @aayushshah15.
Incorrect count of total replicas for AllocatorAdd #41328 Under-replicated ranges when performing sequence of node removes/adds -- @darinpp
storage: system.replication_stats shows faux overreplication #41446 system.replication_stats shows faux overreplication @andreimatei
storage: replication reports generation takes 20% of a node's CPU for 200k ranges #41609 replication reports generation takes 20% of a node's CPU for 200k ranges @andreimatei
BETA BLOCKERS The "old replicaID state reuse" fallout cluster:
BETA BLOCKER roachtest: clearrange/checks=false failed #38772 (roachtest: clearrange/checks=false failed) @nvanbenschoten
teamcity: failed test: bank/zerosum-splits #41096 (had non-voter replicas assertion fired) @danhhz
BETA BLOCKER roachtest: jepsen/monotonic/majority-ring-start-kill-2 failed #41364 Jepsen/monotonic failures
storage: check whether the acquiring replica can receive the lease #42068 leases can be transferred to replicas which are being removed @ajwerner
Probably not blockers, but here for visibility and discussion:
CRDB on Windows has severe issues
Note, #32415 is a lower priority than the above
BulkIO
descriptor changed
(during IMPORT) @pbardearoachtest: import/tpcc/warehouses=1000/nodes=4 failed #39726 roachtest: import/tpcc/warehouses=1000/nodes=4 failed @lucy-zhang(not a release blocker)SQL
Storage
Other Discussion
The text was updated successfully, but these errors were encountered: