-
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
roachtest: kv/splits/nodes=3/quiesce=false failed #31125
Comments
Fell apart as expected. fatal error: runtime: out of memory is the final outcome. What's interesting is that the closed timestamp code seems to really matter:
This is somewhat unexpected because this code should scale like the number of active ranges (active as in, max lease index grows). But perhaps, due to the lease requests that no doubt all ranges are trying to send due to the cluster falling over, the LAIs actually grow. Two take-aways here: that code should try to allocate less (or at least bulk allocate the map), and we should look into not assigning a LAI for LeaseRequest (which we do today just because). |
Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=970685&tab=buildLog
|
Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=985074&tab=buildLog
|
Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=993605&tab=buildLog
|
Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=995412&tab=buildLog
|
Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=997430&tab=buildLog
|
Parameters: To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=1044826&tab=buildLog
|
SHA: https://github.com/cockroachdb/cockroach/commits/dc0e73c728e533fdb3bec63e53eec174e920ff22
Parameters:
To repro, try:
Failed test: https://teamcity.cockroachdb.com/viewLog.html?buildId=952220&tab=buildLog
The text was updated successfully, but these errors were encountered: