Quantcast
Channel: MySQL Forums - NDB clusters
Viewing all articles
Browse latest Browse all 1560

DROP database does not propagate after mysqld restore (1 reply)

$
0
0
I use MySQL Cluster 7.1.8 on CentOS 5.5 in configuration with two ndbd, two mysqld and two ndb_mgmd daemons and faced with following problem. I have create database (testdb1) when all daemons are running and belong to one MySQL cluster. I saw this database (testdb1) on all mysqld. Then I stopped one mysqld daemon and dropped database, created before (testdb1) and created new database (testdb2) on second mysqld. Then started mysqld, stopped before and see databases, existing on it. I see both (testdb1 and testdb2). I didn't expect to see dropped database (testdb1). Could you explain me this situation. This is a bug or designed behaviour?
With tables I have no such problem. Both instructions (create and drop table) propagate on restored mysqld daemon.

Viewing all articles
Browse latest Browse all 1560

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>