mysql-cluster

问题 Below is the update query/query plan that is not using the compound index that was created recently. The explain shows that its not using the compound index named radacctupdate which i think will make the update query faster. There are other indexes on table too which are used by other queries. EXPLAIN UPDATE radacct SET acctstoptime = '2017-01-08 11:52:24', acctsessiontime = unix_timestamp('2017-01-08 11:52:24') - unix_timestamp(acctstarttime), acctterminatecause = '', acctstopdelay =

问题 Below is the update query/query plan that is not using the compound index that was created recently. The explain shows that its not using the compound index named radacctupdate which i think will make the update query faster. There are other indexes on table too which are used by other queries. EXPLAIN UPDATE radacct SET acctstoptime = '2017-01-08 11:52:24', acctsessiontime = unix_timestamp('2017-01-08 11:52:24') - unix_timestamp(acctstarttime), acctterminatecause = '', acctstopdelay =

问题 I have MySQL cluster (NDB) containing 2 servers[NodeA and NodeB]. I have another machine having InnoDB[NodeC] outside cluster. NodeA is master for NodeC replication slave. Problem arises when NodeA is down in cluster, and some transaction take place at NodeB of the cluster. When NodeA is again up and running, all data is sync between NodeA and NodeB. [I set sql_slave_skip_counter=1 into NodeC to remove LOST_EVENT error.] But the data is not replicated to NodeC. If after that any transaction

问题 I am going to deal with a huge amount of data in my project. I have read about big data concepts but never used it yet. But reading all those Big Data Documents I am still not sure whether my requirement needs Big Data or is it good to handle with traditional relational database. Here is some information about my DB. My main DB is a repository for different data sources. Each of this data sources deals with same kind of data (data in same domain), but some data sources contain extra fields