-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
More than 160 DDLs in transaction block crashing the server #6855
Comments
Test code from itest-system test suite. Please edit it for running against local server.
|
Closed by mistake. |
Yes creating a lot of tablets has overhead especially in small machines. |
In a recent run, I got "InternalError_('Timed out: Re ad(tablet: c963dbca7de74163b5c0cfeb092e186e, num_ops: 1, num_attempts: 201, txn: 04cdc811-5135-4d8b-a745-4f7782e63774) passed its deadline 79 6.311s (passed: 60.489s): Leader does not have a valid lease. (yb/consensus/consensus.cc:164): This leader has not yet acquired a lease. (tab let server error 15)\n')" error. |
Probably the master crashed here. Can you retry the same experiment but in a colocated database ? |
Jira Link: DB-4864
On a 3RF universe with c5.large type VMs, tried running a test written in Python with psycopg2.
Test does following steps:
Test throws 'Timed out: Read RPC (request call id 25658) to 172.151.59.101:9100 timed out after 14.274s" error after about 160 tables are created.
Creation of 500 tables succeeds if we add "SPLIT INTO 1 TABLETS" option to create table statement.
The text was updated successfully, but these errors were encountered: