Hello.Sorry for so late to reply to you. I think I reproduce this issue.Here are my reproduce steps: 1.start a version 2.6 node with persistence enabled. 2.create 2 tables with "template=replicated". 3.Insert data to 2 tables. 4.Open a connection to make a long time query targeting on first table.This query should not end until we finish our experiment. 5.Open another connection and try to drop first table.This drop operation will be blocked by the long query. 6.Open another connection try to drop second table.This operation will also be blocked. 7.Open another connection try to create second table.Then you can see "table already exists" exception. 8.Open another connection try to drop second table again.Then you can see "Table doesn't exist" exception.
I use dbeaver to do most above steps. I suggested to make drop table operation be first priority in another post:http://apache-ignite-users.70518.x6.nabble.com/Drop-table-operation-should-be-first-priority-td25546.html. Maxim.Pudov wrote > Looks like a bug to me. If you have a reproducer of this issue, please, > share > it. > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
