Hi, "DROP table" operation also destroying an underlying cache. This change should be properly synchronized between all the nodes, that's why it sends a special Discovery message to all nodes with the new minor topology change. Without this, not all nodes in the cluster will know about stopping the cache, which may lead to the undefined behavior, where some nodes still will process operations related to this cache.
Best Regards, Evgenii чт, 22 нояб. 2018 г. в 16:23, yangjiajun <[email protected]>: > Hello. > > According to my understanding,drop table command will block all operations > on the same table.But in my experiment,all update operations slow down when > there is a drop table operation even these operations aren't targeting the > same table.I guess drop table statement causes ignite sync all update > operations.Is my guess right? > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
