Hello,
I am launching cluster-in-a-box using the below docker-compose on my mac.
Cluster starts successfully, but when trying to create a database I get the following error:
“CREATE PARTITION DATABASE for operation CREATE DATABASE failed with error 1883:Leaf Error (127.0.0.1:3307): Available disk space is below the value of ‘minimal_disk_space’ global variable (100 MB). This query cannot be executed.”
I tried to mount my local volume to one of the volumes in the container but it didn’t resolve the problem.
To which path do i need to mount? or other way to resolve this?
Wow, that’s a bug. I just fixed it - should be out shortly in a new release of the cluster in a box image. Once out i’ll ping here. Thanks for the report and your patience.
@ohad please re-pull and use the image memsql/cluster-in-a-box:latest. You will be able to mount /var/lib/memsql as a volume without hitting the same problem you hit before. Of course, make sure that the user in the container has permissions to write to the volume.
Thanks for handling this @carl . However i still can’t create a database.
The mount has worked well this time as you can see - having 67G available disk:
Filesystem Size Used Avail Use% Mounted on
osxfs 234G 152G 67G 70% /var/lib/memsq
but when running “create database unittest;” I get the following errors:
From sequel pro:
CREATE PARTITION DATABASE for operation CREATE DATABASE failed with error 1883:Leaf Error (127.0.0.1:3307): Available disk space is below the value of ‘minimal_disk_space’ global variable (100 MB). This query cannot be executed.
From docker logs:
ERROR: Thread 115045: CreateFileAndAllocateSpace: Failed to allocate space for file logs/unittest_4_staging: 28 (No space left on device).
That looks like the same error as before - the issue may be that I uploaded the fix over the same tag in the docker hub, so you probably need to force re-pull the docker image to get the change.
I tried tried the latest and to be sure i also tried it’s equivalent one centos-7.1.11-6c108deb15-2.0.4-1.8.1 in both i get the following error:
2020-11-06 03:45:09.186018 Initializing MemSQL Cluster in a Box
2020-11-06 03:45:09.186161 Creating…
2020-11-06 03:45:10.259266 Done.
2020-11-06 03:45:10.259347 Configuring…
2020-11-06 03:45:11.331046 Done.
2020-11-06 03:45:11.331368 Bootstrapping…
Latest errors from MemSQL tracelog:
: Failed to connect to MemSQL: process exited: exit status 255
Initialization failed, please fix any issues and re-initialize the container.
Traceback (most recent call last):
File “/startup”, line 101, in
You may need to remove this container before continuing:
docker rm (CONTAINER_NAME)
init_cluster()
File “/startup”, line 45, in init_cluster
ctl(“start-node”, “–all”)
File “/startup”, line 18, in ctl
subprocess.check_output([“memsqlctl”, “-yj”] + list(args)))
File “/usr/lib64/python2.7/subprocess.py”, line 575, in check_output
raise CalledProcessError(retcode, cmd, output=output)
subprocess.CalledProcessError: Command ‘[‘memsqlctl’, ‘-yj’, ‘start-node’, ‘–all’]’ returned non-zero exit status 1
I am not sure what the issue is, however I noticed you are using /tmp for each run - this directory may contain artifacts from previous runs which may be partially corrupted/deleted. Please use an empty directory dedicated to this container, and in the event of an error please clear the directory before restart.
I have successfully run the new CIAB image using /tmp as well as an empty directory without issue.
Hi joseph! This issue has been escalated internally and we’re working on getting the support you need. We appreciate your patience & hope to have an expert in contact with you soon.
