Hot answers tagged

12

Since there is already and answer submitted, and a useful and valid one at that, I do not want to distract from its own usefulness but there are indeed points to raise that go way beyond just a short comment. So consider this "augmentation", which is hopefully valid but primarily in addition to what has already been said. The truth is to really consider "...


11

As per MongoDB BOL Here Changed in version 3.4: Values can range from 256MB to 10TB and can be a float. In addition, the default value has also changed. Starting in 3.4, the WiredTiger internal cache, by default, will use the larger of either: 50% of RAM minus 1 GB, or 256 MB. With WiredTiger, MongoDB utilizes both the WiredTiger internal cache and the ...


7

Actually, if you look closely, it's not mongod that dies for "out-of-memory", it's the kernel OOM (out of memory) manager that kills mongod, because it has the biggest memory usage. Yes, you can try to solve the problem with monngodb configuration parameter cacheSizeGB, but in the container environment, it is better to use cgroups to limit the resources ...


7

You have been hacked, and are now mining cryptocurrency for the hacker. They got in by guessing the password for your postgresql server's super-user account. Then they used the lo_export facility to drop the binary for a user-defined-function which executes arbitrary shell commands. That is what fun308928987 is, the SQL function which was created to wrap ...


7

I gather that Oracle XE only gives you a single database Correct - as long as you "speak" Oracle-ese. The Container Database is the only "real" Oracle Database instance that you have. The "Pluggable Databases" within it are essentially "Tablespaces on Steroids", but with much better security that now guarantees the ...


6

It's sensible to think about how to scale your application in future, but you can start with a simpler deployment that can grow with your requirements. what should i choose? having 1 database sounds good as it will save me a lot of resources and will make my life easier, but separating the services to many database sound logic to me as one service don't ...


6

As it turns out this was indeed a Docker problem rather than MySQL. Vanilla MySQL image is built on Debian 9 and by default it lacks UTF-8 support. So I had to follow these steps: Login into Docker container with docker exec -it mysql1 bash and run apt-get update Then run apt-get install vim apt-get install locales Run dpkg-reconfigure locales and select ...


5

Since best practice also suggest that "The appropriate number of mongos processes will depend on the nature of the application and deployment" I started to wonder whether our usage of mongos actually appropriate I think this is a question that ultimately only you can answer, as the documentation refers to. One of the recommended strategies is to have ...


4

This is a known issue: mapping volumes on Macs isn't supported yet. You can follow that Github issue for more news, like when it's fixed. Until then, no, people aren't doing anything more than simple testing with that combination of tools (Mac, Docker, Linux, SQL Server). If you need to do real, productive development on a platform that's supported today, ...


4

Is the code shown under "Relevant code:" (in the question) the exact code being executed, as in copied and pasted into here and not re-typed? I ask because the file extension on the sqlserver_backup_cert file is different between the BACKUP and CREATE (i.e. restore) statements. It is backed-up as .cer but then you are looking for .crt in the CREATE. Also, ...


4

Short answer: Nothing. Long answer: "Latest" refers to be the latest, which is 10.5.y; some day soon it may refer to the latest 10.6.y, which is is early stages of being released. 10 refers to the lastest 10.x.y 10.5 refers to the latest 10.5.y 10.5.11 seems to be the latest available 10.5.y "Focal" refers to the base OS the Docker ...


3

OK, so show processlist; revealed that some queries got stuck in "Waiting to lock metadata" on that table. show engine innodb status \G helped identify the offending transaction and then simple KILL <id> unlocked the system.


3

The key difference here is whether SSMS/SMO is attempting to connect with IPv4 or IPv6. If you do a ping localhost in a command prompt, you should see it resolve to ::1, which is the IPv6 equivalent of 127.0.0.1. Connecting to . does the same thing. Your docker run command only exposes port 1433 on 127.0.0.1. You can verify this by running netstat -a to see ...


3

This is most likely a RAM starvation issue. Things to check: Does the container have 4 GB of RAM assigned to it? Check this answer. Have you configured the Max Server Memory setting for SQL Server inside the container? Depending on how much RAM SQL Server can see in the container, this might be set to anything from 1 GB to 3.25 GB. Is your host's RAM used ...


3

With "quiet" configuration parameter (not recommended) you get rid of: "Successfully authenticated as..." "connection accepted from ..." but "end connection ..." still stays there and there is no way to remove it, without changing source code. You can always ask developers to change code to if (!quiet) { const auto word = (connectionCount == 1 ? " ...


3

The warning is useful because it tells you that this proxy privileges will never be matched. Your options are: you delete this privilege you change the @ part to % or to a defined ip address you disable skip-name-resolve (which will slow down MySQL, which will now depend on the DNS resolver speed: https://dev.mysql.com/doc/refman/5.7/en/host-cache.html) ...


3

It sounds like you're new to Docker. You may want to spend some time reading through documentation and examples to get a better feel for how things work. First, simply installing software doesn't necessarily make it run, and that is certainly the case with CentOS and other Red Hat variants. On a bare metal host, you would simply run systemctl start mariadb ...


3

Also, you just can run CHANGE MASTER TO GET_MASTER_PUBLIC_KEY=1; but this solution has a restriction (see the documentation https://dev.mysql.com/doc/refman/8.0/en/caching-sha2-pluggable-authentication.html) Use of a trusted local copy of the public key enables the client to avoid a round trip in the client/server protocol, and is more secure than ...


3

For anyone else who is new to running SQL Server in a macOS Docker container, you first need to find out your Docker container ID. The commands will be like this: List Docker info: $ docker container ls 47940489ee07 Copy from the macOS directory to the Docker container directory: $ docker cp /Users/Trump/snp500-companies.csv 47940489ee07:/snp500-company-...


3

There are two things that use shared memory: The shared memory that is allocated at server start. This consists of several parts, but the lion's share is shared_buffers, the data cache. So you have to have more shared memory than that. Shared memory segments allocated by parallel query to communicate between parallel workers. Their size depends on the data ...


3

Docker images tagged with latest contain the latest release at the time you retrieve it (this is Docker's convention), thus the image in the source contains different TimescaleDB's version (1.6.0) than in the current latest image (2.1.0 is latest now). This leads into the error of missing binary, since the images are not the same and the current latest image ...


3

From the top output: load average: 0.94, 0.55, 0.51 Those are the average CPU utilization over the last 1, 5, and 15 minutes. So...it doesn't seem like SQL Server is using a huge amount of resources based on your screenshot (assuming two CPUs). The 3rd line also shows 87.9 % idle time on the CPU. You commented: the point is that when no load exists for ...


2

I ended up deleting the tc.log file in /var/lib/mysql. When I started mysql again, it created a new tc.log and started up. sudo rm -f /var/lib/mysql/tc.log


2

In normal situation, mongodb uses always all available memory!! However, you can limit mongo's memory using cgroup. Here is presentation what may help too.


2

I think that the problem could be that you don't set the CASSANDRA_BROADCAST_ADDRESS parameter that is used by Cassandra when it talks with other nodes. By default it sets it to value of CASSANDRA_LISTEN_ADDRESS, but in your case this address is address of Docker network, so other nodes won't able to reach your Docker instance. You need to set ...


2

HA implies that something will break. But if all the pieces are in the same server, it seems like the most likely thing to break is the server -- taking down everything. For HA to be really effective, you need separate servers geographically separated. A blend would be to have such separate servers, then have dockers in each. This could, for example, ...


2

First of all are the containers visible to one another i.e. can you ping the mysql box from the webserver? If not it is a visibility issue, try creating a docker network to put the two containers within. First create a docker network: docker network create lamp-network You can see this by the following command: docker network ls Now start your two ...


2

Those messages are unrelated. The first one will show up every time you start postgresql if your machine is not configured to use IPv6. You can just ignore it if you don't care about IPv6. The other one is a bit more complex. 'system was not properly shut down' means it was interrupted without being given a chance to do a checkpoint and shut down. '...


2

I've come up with an answer for this - it seems like a bit of a hack, but it seems to work. To recap: the goal was to set up a master with a single slave using MariaDB 10.3.4 (in Docker containers, although this isn't necessarily a requirement) from scratch (ie. newly-installed, empty databases), so that the system will simply start up and work without any ...


Only top voted, non community-wiki answers of a minimum length are eligible