-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
pkg/sql/logictest/tests/cockroach-go-testserver-24.3/cockroach-go-testserver-24_3_test: TestLogic_upgrade failed #139405
Comments
This looks similar to #139405 |
pkg/sql/logictest/tests/cockroach-go-testserver-24.3/cockroach-go-testserver-24_3_test.TestLogic_upgrade failed on release-25.1 @ 4bb718e70117615cd5ac3210ae9dcfcd67097ab7: Fatal error:
Stack:
Log preceding fatal error
Parameters:
Same failure on other branches
|
Previusly, the lease manager allowed descriptors to be leased before the range feed was fully initialized. This was problematic because if an descriptor was updated before the range feed is started we would have no way of knowing. For example an early query during startup could fetch the system database descriptor before the range feed starts, and this could kept forever. If an upgrade bumped the descriptor version between the initial fetch and start of range feed then we could end up with a node stuck with the sale version forever. To address this, this patch forces any early lease acqusitions to wait for the range feed to start up. Fixes: cockroachdb#139837 Fixes: cockroachdb#139405 Fixes: cockroachdb#139356 Fixes: cockroachdb#139100 Release note: None
Previusly, the lease manager allowed descriptors to be leased before the range feed was fully initialized. This was problematic because if an descriptor was updated before the range feed is started we would have no way of knowing. For example an early query during startup could fetch the system database descriptor before the range feed starts, and this could kept forever. If an upgrade bumped the descriptor version between the initial fetch and start of range feed then we could end up with a node stuck with the sale version forever. To address this, this patch forces any early lease acqusitions to wait for the range feed to start up. Fixes: cockroachdb#139837 Fixes: cockroachdb#139405 Fixes: cockroachdb#139356 Fixes: cockroachdb#139100 Release note: None
Previusly, the lease manager allowed descriptors to be leased before the range feed was fully initialized. This was problematic because if an descriptor was updated before the range feed is started we would have no way of knowing. For example an early query during startup could fetch the system database descriptor before the range feed starts, and this could kept forever. If an upgrade bumped the descriptor version between the initial fetch and start of range feed then we could end up with a node stuck with the sale version forever. To address this, this patch forces any early lease acqusitions to wait for the range feed to start up. Fixes: cockroachdb#139837 Fixes: cockroachdb#139405 Fixes: cockroachdb#139356 Fixes: cockroachdb#139100 Release note: None
Previusly, the lease manager allowed descriptors to be leased before the range feed was fully initialized. This was problematic because if an descriptor was updated before the range feed is started we would have no way of knowing. For example an early query during startup could fetch the system database descriptor before the range feed starts, and this could kept forever. If an upgrade bumped the descriptor version between the initial fetch and start of range feed then we could end up with a node stuck with the sale version forever. To address this, this patch forces any early lease acqusitions to wait for the range feed to start up. Fixes: cockroachdb#139837 Fixes: cockroachdb#139405 Fixes: cockroachdb#139356 Fixes: cockroachdb#139100 Release note: None
Previusly, the lease manager allowed descriptors to be leased before the range feed was fully initialized. This was problematic because if an descriptor was updated before the range feed is started we would have no way of knowing. For example an early query during startup could fetch the system database descriptor before the range feed starts, and this could kept forever. If an upgrade bumped the descriptor version between the initial fetch and start of range feed then we could end up with a node stuck with the sale version forever. To address this, this patch forces any early lease acqusitions to wait for the range feed to start up. Fixes: cockroachdb#139837 Fixes: cockroachdb#139405 Fixes: cockroachdb#139356 Fixes: cockroachdb#139100 Release note: None
140058: catalog/lease: disallow leases until range feed starts r=fqazi a=fqazi Previusly, the lease manager allowed descriptors to be leased before the range feed was fully initialized. This was problematic because if an descriptor was updated before the range feed is started we would have no way of knowing. For example an early query during startup could fetch the system database descriptor before the range feed starts, and this could kept forever. If an upgrade bumped the descriptor version between the initial fetch and start of range feed then we could end up with a node stuck with the sale version forever. To address this, this patch forces any early lease acqusitions to wait for the range feed to start up. Fixes: #139837 Fixes: #139405 Fixes: #139356 Fixes: #139100 Informs: #139837 Informs: #139405 Informs: #139356 Release note: None Co-authored-by: Faizan Qazi <faizan@cockroachlabs.com>
140058: catalog/lease: disallow leases until range feed starts r=fqazi a=fqazi Previusly, the lease manager allowed descriptors to be leased before the range feed was fully initialized. This was problematic because if an descriptor was updated before the range feed is started we would have no way of knowing. For example an early query during startup could fetch the system database descriptor before the range feed starts, and this could kept forever. If an upgrade bumped the descriptor version between the initial fetch and start of range feed then we could end up with a node stuck with the sale version forever. To address this, this patch forces any early lease acqusitions to wait for the range feed to start up. Fixes: #139837 Fixes: #139405 Fixes: #139356 Fixes: #139100 Informs: #139837 Informs: #139405 Informs: #139356 Release note: None Co-authored-by: Faizan Qazi <faizan@cockroachlabs.com>
140058: catalog/lease: disallow leases until range feed starts r=fqazi a=fqazi Previusly, the lease manager allowed descriptors to be leased before the range feed was fully initialized. This was problematic because if an descriptor was updated before the range feed is started we would have no way of knowing. For example an early query during startup could fetch the system database descriptor before the range feed starts, and this could kept forever. If an upgrade bumped the descriptor version between the initial fetch and start of range feed then we could end up with a node stuck with the sale version forever. To address this, this patch forces any early lease acqusitions to wait for the range feed to start up. Fixes: #139837 Fixes: #139405 Fixes: #139356 Fixes: #139100 Informs: #139837 Informs: #139405 Informs: #139356 Release note: None Co-authored-by: Faizan Qazi <faizan@cockroachlabs.com>
Previusly, the lease manager allowed descriptors to be leased before the range feed was fully initialized. This was problematic because if an descriptor was updated before the range feed is started we would have no way of knowing. For example an early query during startup could fetch the system database descriptor before the range feed starts, and this could kept forever. If an upgrade bumped the descriptor version between the initial fetch and start of range feed then we could end up with a node stuck with the sale version forever. To address this, this patch forces any early lease acqusitions to wait for the range feed to start up. Fixes: #139837 Fixes: #139405 Fixes: #139356 Fixes: #139100 Release note: None
Based on the specified backports for linked PR #140058, I applied the following new label(s) to this issue: branch-release-24.3. Please adjust the labels as needed to match the branches actually affected by this issue, including adding any known older branches. 🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf. |
Previously, the lease manager allowed descriptors to be leased before the range feed was fully initialized. This was problematic because if an descriptor was updated before the range feed is started we would have no way of knowing. For example an early query during startup could fetch the system database descriptor before the range feed starts, and this could kept forever. If an upgrade bumped the descriptor version between the initial fetch and start of range feed then we could end up with a node stuck with the sale version forever. To address this, this patch forces any early lease acqusitions to wait for the range feed to start up. Fixes: cockroachdb#139837 Fixes: cockroachdb#139405 Fixes: cockroachdb#139356 Fixes: cockroachdb#139100 Release note: None
pkg/sql/logictest/tests/cockroach-go-testserver-24.3/cockroach-go-testserver-24_3_test.TestLogic_upgrade failed on release-25.1 @ 29c0a3d5161b6818e414efc9c35321c1c0416e19:
Fatal error:
Stack:
Log preceding fatal error
Parameters:
attempt=1
run=5
shard=1
Help
See also: How To Investigate a Go Test Failure (internal)
Same failure on other branches
This test on roachdash | Improve this report!
Jira issue: CRDB-46634
The text was updated successfully, but these errors were encountered: