Skip to content

[DocDB] Drop table fails with "could not serialize access due to concurrent update" while running transactional workload with NodeRestart Nemesis #27649

Open
@dhruva4869

Description

@dhruva4869

Jira Link: DB-17237

Description

Version: 2.27.0.0-b196
Steps:

  1. Run Sample app to create tables
  2. Extra tables are created, inherited tables are created.
  3. Add extra columns, create functions and triggers.
  4. Run Sample App to load data into the tables
  5. Start nemesis NodeRestart
  6. While workload is running perform the following scenarios:
    i. Perform CREATE INDEX Queries, verify
    ii. CREATE ROLES and verify
    iii. GRANT permissions to ROLES and verify
    iv. CREATE Materialized Views.
    v. Drop partition tables
    vi. Execute DMLs (INSERT/UPDATE/DELETE) to validate changes.
    vii. Drop indexes
    viii. Drop tables

Step 6. viii. intermittently fails with

 ERROR:  could not serialize access due to concurrent update\n', 'DETAIL:  6a4c6a8b-4a89-4e8f-8ebf-82d09bb1af79 conflicts with same priority transaction (pri: 18446744073709551615): 763edae8-0130-4fe3-8a9a-44385819a59c\n'

Issue Type

kind/bug

Warning: Please confirm that this issue does not contain any sensitive information

  • I confirm this issue does not contain any sensitive information.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions