Tag Info

New answers tagged

0

There is actually nothing really wrong here, at least not based on what you have included in the question. Go back to this point: ubuntu-user@ubuntu-vm:~$ mongo MongoDB shell version: 3.0.1 connecting to: test Server has startup warnings: 2015-03-27T12:37:30.430+0100 I CONTROL [initandlisten] 2015-03-27T12:37:30.430+0100 I CONTROL [initandlisten] ** ...


0

If you want to recover by filetype, please note the following structure in MySql database file system: A MySQL table is the combination of three files: The FRM file is the table definition. The MYD file is where the actual data is stored. The MYI file is where the indexes created on the table are stored. Source: [1] ...


1

Not an elegant solution but after installing the package using apt-get (which fails creating the cluster but installs PostgreSQL), I switched to the postgres user and created the database using initdb. Then back to root, I created the cluster using the pg_createcluster command. This moved the configurations to /etc/postgres/9.4/main and set it all up.


0

The issue was a result of having different values for replSet in /etc/mongod.conf. I thought the servers should be named uniquely -- this is incorrect. Each server in the replicaset must have the same value for replSet.


0

Shut down mysql. What files do you see? Restart mysql; are things better now? One possible fix is to CREATE a new table (with a different name), copy the .frm to somewhere else, drop the table, shutdown, copy the .frm back as the problematical table name, restart.


0

I have addressed this once before : MySQL database drop insanely slow My suggestion in that post was this SET unique_checks = 0; SET foreign_key_checks = 0; SET GLOBAL innodb_stats_on_metadata = 0; DROP DATABASE db_madeintouch; SET GLOBAL innodb_stats_on_metadata = 1; SET foreign_key_checks = 1; SET unique_checks = 1; If all your data uses InnoDB, this ...


0

The number of cores should not be relevant. What else is different? MySQL version? Operating system brand? OS version? Filesystem (ext3, ext4, zfs, etc)? DROP DATABASE has to do a lot of filesystem work, so that is what I would suspect. Ditto for TRUNCATE. Why are you doing a lot of DROPs and TRUNCATEs?



Top 50 recent answers are included