distsql: next range doesn't cover last end key panic #15352
Description
I was adding some tests while working on a change and I ran into this panic. It looks like the first range returned by the SpanResolver doesn't include the start key.
I170426 09:26:16.650506 1111 kv/leaseholder_cache.go:56 [client=127.0.0.1:58916,user=root,n1] lookup lease holder for r10: {5 5 2}
I170426 09:26:16.650516 1111 kv/leaseholder_cache.go:56 [client=127.0.0.1:58916,user=root,n1] lookup lease holder for r21: {1 1 2}
I170426 09:26:16.650523 1111 kv/leaseholder_cache.go:61 [client=127.0.0.1:58916,user=root,n1] lookup lease holder for r22: not found
I170426 09:26:16.650533 1111 kv/leaseholder_cache.go:61 [client=127.0.0.1:58916,user=root,n1] lookup lease holder for r22: not found
F170426 09:26:16.650590 1111 sql/distsql_physical_planner.go:425 [client=127.0.0.1:58916,user=root,n1] next range /Table/5{2/1/99-3/1/0} doesn't cover last end key /Table/52/1. Splits: []sql.spanPartition{}
Metadata
Metadata
Assignees
Labels
No labels