Skip to content

Fix deadlocks during table registratin/deregistration#34

Merged
osipovartem merged 1 commit into
mainfrom
aosipov/fix_locks
Nov 22, 2025
Merged

Fix deadlocks during table registratin/deregistration#34
osipovartem merged 1 commit into
mainfrom
aosipov/fix_locks

Conversation

@osipovartem
Copy link
Copy Markdown
Contributor

No description provided.

@DanCodedThis
Copy link
Copy Markdown
Contributor

DanCodedThis commented Nov 22, 2025

@osipovartem When I try to create a table that already exists, I get this error:

 > SHOW TABLES;

Error occurred: 010001 (02000): 97918652-5c44-4f0b-99e7-38e83b31ba3b: External error: Table next not found.
 > CREATE TABLE embucket.public.dan (name Varchar);

Error occurred: 010001 (02000): c595d368-e9bd-49f1-a34a-d9ae2aeb086f: Iceberg error: service error
 > CREATE TABLE embucket.public.dandandan (name Varchar);

Error occurred: 010001 (02000): c51244c1-2313-4afd-a3aa-2328d50e5b1e: Iceberg error: service error
 > SHOW TABLES;
+--------------------------------------------------------------+
| created_on | name      | kind  | database_name | schema_name |
|------------+-----------+-------+---------------+-------------|
| None       | dan       | TABLE | embucket      | public      |
| None       | dandandan | TABLE | embucket      | public      |
+--------------------------------------------------------------+

KEEP IN MIND If you create first time and use SHOW TABLES everything works fine as long as you don't restart the service.

For example, you can do this:

 > CREATE TABLE embucket.public.dandandan (name Varchar);

Error occurred: 010001 (02000): 576f7be9-9fb2-4104-b4c4-ad61a993c6fb: Iceberg error: service error
 > SHOW TABLES;
+--------------------------------------------------------------+
| created_on | name      | kind  | database_name | schema_name |
|------------+-----------+-------+---------------+-------------|
| None       | dandandan | TABLE | embucket      | public      |
+--------------------------------------------------------------+

HOWEVER, probably this is related more to #32 than this bug.

Copy link
Copy Markdown
Contributor

@DanCodedThis DanCodedThis left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@osipovartem
Copy link
Copy Markdown
Contributor Author

@osipovartem When I try to create a table that already exists, I get this error:

 > SHOW TABLES;

Error occurred: 010001 (02000): 97918652-5c44-4f0b-99e7-38e83b31ba3b: External error: Table next not found.
 > CREATE TABLE embucket.public.dan (name Varchar);

Error occurred: 010001 (02000): c595d368-e9bd-49f1-a34a-d9ae2aeb086f: Iceberg error: service error
 > CREATE TABLE embucket.public.dandandan (name Varchar);

Error occurred: 010001 (02000): c51244c1-2313-4afd-a3aa-2328d50e5b1e: Iceberg error: service error
 > SHOW TABLES;
+--------------------------------------------------------------+
| created_on | name      | kind  | database_name | schema_name |
|------------+-----------+-------+---------------+-------------|
| None       | dan       | TABLE | embucket      | public      |
| None       | dandandan | TABLE | embucket      | public      |
+--------------------------------------------------------------+

KEEP IN MIND If you create first time and use SHOW TABLES everything works fine as long as you don't restart the service.

For example, you can do this:

 > CREATE TABLE embucket.public.dandandan (name Varchar);

Error occurred: 010001 (02000): 576f7be9-9fb2-4104-b4c4-ad61a993c6fb: Iceberg error: service error
 > SHOW TABLES;
+--------------------------------------------------------------+
| created_on | name      | kind  | database_name | schema_name |
|------------+-----------+-------+---------------+-------------|
| None       | dandandan | TABLE | embucket      | public      |
+--------------------------------------------------------------+

HOWEVER, probably this is related more to #32 than this bug.

To recreate the table you need to call CREATE OR REPLACE

@DanCodedThis
Copy link
Copy Markdown
Contributor

@osipovartem It's more of a registering it back so that metastore would be able to list it thing. But regardless, I think we can merge this!

@osipovartem osipovartem merged commit 1466cd1 into main Nov 22, 2025
3 checks passed
@osipovartem osipovartem deleted the aosipov/fix_locks branch November 22, 2025 14:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants