GithubHelp home page GithubHelp logo

docker-mariadb-cluster's People

Contributors

toughiq avatar

Stargazers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Watchers

avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar avatar

Forkers

mtahiue mulderh barnumd hafeez3000 atchariya judypol nevalla junlapong haijunsu sysc0d murf butonic zx1986 ovanassche ngocngv dottgonzo ziguilp imjerrybao vqiu nekulin xingjiudong dockeraa hydracz limweb bluemutedwisdom ethan-2017 hitomidennis jay74jung ly798 animalcarpet agungsijawir zhangjianasp rtheobald yelmir kerrer tanzhiliangit wilsonliu78 piyapsri docker-craft streetracer48 foleymic mckatoo blue-cosmos droidwiki duong1989 tamasgal mortn comdata gurjindersingh wolvenspirit changsongyang cheeraccident moussdia andersonbr-oss hummans dsilabs renowncoder georg480 locvfx nikitasardov maorin flamesrunner jeffyoungl swisslearninghub itdataengsirim

docker-mariadb-cluster's Issues

MariaDB crashes on multi-node cluster

If you run the cluster on a single node, just initialized by docker swarm init, everything works as expected.
But as soon as the cluster consists of more than one node, connected by the created overlay network, the dbcluster instances, which get started on different hosts than the bootstrap container, will crash at/after syncing with the bootstrap server.

can't use mode global

Hi,
after some days spent on docker swarm, i'm happy to not have persistent volumes and to see that with many replicas all works good. There is another issue that could cause loosing data on cluster. If i need to boot first 1 replica, and then scale, i can't set global mode in docker swarm (because it start all the replicas contemporary), and with the replicated mode is possible that all the replicas are on the same node, so shutting down the node will delete everything.
The only one solution (not tested), is to enable global mode, but costrain the service to run on node with certain label and initially set it only on one node, and then adding that label to more nodes. The best is to be able to start all the replicas together. Is possible to fix this issue?

Adding healtcheck in docker compose file caused the container to fail

Hi,

I'm running docker 1.13 experimental and use compose file to deploy mariadb in cluster using your image.
The docker compose file looks like:

version: '3'
services:
    mariadb:
      deploy:
        replicas: 1
      image: ${DOCKER_REPOSITORY}openpaas/toughiq/mariadb-cluster:2.0
      networks:
        - default
      volumes:
        - /config/mariadb/maria.cnf:/etc/mysql/conf.d/maria.cnf
      healthcheck:
          test: ["CMD", "ls"]
          interval: 30s
          timeout: 1m30s
          retries: 5
      environment:
        - DB_SERVICE_NAME=mariadb
        - MYSQL_ROOT_PASSWORD=xxxx
        - MYSQL_DATABASE=yyyyy
        - MYSQL_USER=user1
        - MYSQL_PASSWORD=user1

If i put the healthcheck test, the mariadb container failed after 10 sec, and the last line of the log shows:
/usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init_cluster_conf.sh
If I removed the healthcheck test, the mariadb container succeeds running.
BTW, the healthcheck is a dummy check and no matter what i put in the command it causes the container to fail.

Do you have any idea about the reason of the crash ? It works me fine for other container (not mariadb).

Thanks

Pulse check

It's been a minute since this repo saw a commit. As a result, I have two questions:

  • Who's using this in production with something like wordpress-swarm?
  • Other than persistence, are there any glaring needs left to call this product stable?

Using in production.

Hi,

I'm trying to find reliable solution to run SQL cluster in docker swarm. So it turns out that this project provides probably the easiest way to do that. But as mentioned in README file, it's not ready for production. So I would like to know, if there are any other projects like this you will recommend and what issues will I face if I use this project in production?

When reboot master db node then can not join back to the old cluster

Hi,
I run the cluster in 3 db nodes. and initially, the replica is 1 then i scale to 3. So 3 db containers running on 3 physical nodes separately without any issue.
later I reboot docker swarm manager also the node1 master db host. then the db cluster can not join back.
Is anyone have this issue?

This is not mariadb detected

If you connect to this cluster server with mariadb using on navicat 11.1.12.
80270006: This is not MariaDB server.

why? and cant add tag mariadb configuration for my.cnf?

Node not detected on maxscale

Hi
first of all thanks for really good instruction .

i have been using cluster on test environment and i'v done db cluster running . but when i use maxscale , it's show all servers down state .

is there any network issue or it's about maxscale ?

i can access nodes within ip on new network created and still have access to maxscale .

Service fails on startup

First of all, thanks for your work. If this one is running, it would be a very nice piece of my docker toolkit. But actually use with the following docker-compose file fails

version: "3"
services:

  database:
    image: toughiq/mariadb-cluster:10.1
    environment:
      DB_SERVICE_NAME: database
      MYSQL_ROOT_PASSWORD: 12345678
      MYSQL_DATABASE: test
      MYSQL_USER: test
      MYSQL_PASSWORD: 12345678

running docker-compose up database gives me the following output

database_1  | Initializing database
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] /usr/sbin/mysqld (mysqld 10.1.29-MariaDB-1~jessie) starting as process 64 ...
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: Using mutexes to ref count buffer pool pages
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: The InnoDB memory heap is disabled
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: Compressed tables use zlib 1.2.8
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: Using Linux native AIO
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: Using SSE crc32 instructions
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: Initializing buffer pool, size = 256.0M
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: Completed initialization of buffer pool
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: The first specified data file ./ibdata1 did not exist: a new database to be created!
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: Setting file ./ibdata1 size to 12 MB
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: Setting log file ./ib_logfile101 size to 48 MB
database_1  | 2017-12-14 11:31:32 139802196658112 [Note] InnoDB: Setting log file ./ib_logfile1 size to 48 MB
database_1  | 2017-12-14 11:31:33 139802196658112 [Note] InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
database_1  | 2017-12-14 11:31:33 139802196658112 [Warning] InnoDB: New log files created, LSN=45781
database_1  | 2017-12-14 11:31:33 139802196658112 [Note] InnoDB: Doublewrite buffer not found: creating new
database_1  | 2017-12-14 11:31:33 139802196658112 [Note] InnoDB: Doublewrite buffer created
database_1  | 2017-12-14 11:31:33 139802196658112 [Note] InnoDB: 128 rollback segment(s) are active.
database_1  | 2017-12-14 11:31:33 139802196658112 [Warning] InnoDB: Creating foreign key constraint system tables.
database_1  | 2017-12-14 11:31:33 139802196658112 [Note] InnoDB: Foreign key constraint system tables created
database_1  | 2017-12-14 11:31:33 139802196658112 [Note] InnoDB: Creating tablespace and datafile system tables.
database_1  | 2017-12-14 11:31:33 139802196658112 [Note] InnoDB: Tablespace and datafile system tables created.
database_1  | 2017-12-14 11:31:33 139802196658112 [Note] InnoDB: Waiting for purge to start
database_1  | 2017-12-14 11:31:33 139802196658112 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 0
database_1  | 2017-12-14 11:31:33 139801361643264 [Note] InnoDB: Dumping buffer pool(s) not yet started
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] /usr/sbin/mysqld (mysqld 10.1.29-MariaDB-1~jessie) starting as process 92 ...
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: Using mutexes to ref count buffer pool pages
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: The InnoDB memory heap is disabled
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: Compressed tables use zlib 1.2.8
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: Using Linux native AIO
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: Using SSE crc32 instructions
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: Initializing buffer pool, size = 256.0M
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: Completed initialization of buffer pool
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: Highest supported file format is Barracuda.
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: 128 rollback segment(s) are active.
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB: Waiting for purge to start
database_1  | 2017-12-14 11:31:36 140641052444608 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 1616697
database_1  | 2017-12-14 11:31:36 140640235026176 [Note] InnoDB: Dumping buffer pool(s) not yet started
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] /usr/sbin/mysqld (mysqld 10.1.29-MariaDB-1~jessie) starting as process 121 ...
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: Using mutexes to ref count buffer pool pages
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: The InnoDB memory heap is disabled
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: Compressed tables use zlib 1.2.8
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: Using Linux native AIO
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: Using SSE crc32 instructions
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: Initializing buffer pool, size = 256.0M
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: Completed initialization of buffer pool
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: Highest supported file format is Barracuda.
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: 128 rollback segment(s) are active.
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB: Waiting for purge to start
database_1  | 2017-12-14 11:31:39 140338210944960 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 1616707
database_1  | 2017-12-14 11:31:39 140337393694464 [Note] InnoDB: Dumping buffer pool(s) not yet started
database_1  | 
database_1  | PLEASE REMEMBER TO SET A PASSWORD FOR THE MariaDB root USER !
database_1  | To do so, start the server, then issue the following commands:
database_1  | 
database_1  | '/usr/bin/mysqladmin' -u root password 'new-password'
database_1  | '/usr/bin/mysqladmin' -u root -h  password 'new-password'
database_1  | 
database_1  | Alternatively you can run:
database_1  | '/usr/bin/mysql_secure_installation'
database_1  | 
database_1  | which will also give you the option of removing the test
database_1  | databases and anonymous user created by default.  This is
database_1  | strongly recommended for production servers.
database_1  | 
database_1  | See the MariaDB Knowledgebase at http://mariadb.com/kb or the
database_1  | MySQL manual for more instructions.
database_1  | 
database_1  | Please report any problems at http://mariadb.org/jira
database_1  | 
database_1  | The latest information about MariaDB is available at http://mariadb.org/.
database_1  | You can find additional information about the MySQL part at:
database_1  | http://dev.mysql.com
database_1  | Consider joining MariaDB's strong and vibrant community:
database_1  | https://mariadb.org/get-involved/
database_1  | 
database_1  | Database initialized
database_1  | MySQL init process in progress...
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] mysqld (mysqld 10.1.29-MariaDB-1~jessie) starting as process 154 ...
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: Using mutexes to ref count buffer pool pages
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: The InnoDB memory heap is disabled
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: Compressed tables use zlib 1.2.8
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: Using Linux native AIO
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: Using SSE crc32 instructions
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: Initializing buffer pool, size = 256.0M
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: Completed initialization of buffer pool
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: Highest supported file format is Barracuda.
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: 128 rollback segment(s) are active.
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB: Waiting for purge to start
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.36-82.2 started; log sequence number 1616717
database_1  | 2017-12-14 11:31:42 139938746070784 [Note] InnoDB: Dumping buffer pool(s) not yet started
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] Plugin 'FEEDBACK' is disabled.
database_1  | 2017-12-14 11:31:42 139939563587520 [Warning] 'user' entry 'root@eca312c9edad' ignored in --skip-name-resolve mode.
database_1  | 2017-12-14 11:31:42 139939563587520 [Warning] 'proxies_priv' entry '@% root@eca312c9edad' ignored in --skip-name-resolve mode.
database_1  | 2017-12-14 11:31:42 139939563587520 [Note] mysqld: ready for connections.
database_1  | Version: '10.1.29-MariaDB-1~jessie'  socket: '/var/run/mysqld/mysqld.sock'  port: 0  mariadb.org binary distribution
database_1  | Warning: Unable to load '/usr/share/zoneinfo/leap-seconds.list' as time zone. Skipping it.
database_1  | 2017-12-14 11:31:43 139939562720000 [Warning] 'proxies_priv' entry '@% root@eca312c9edad' ignored in --skip-name-resolve mode.
database_1  | 2017-12-14 11:31:43 139939562720000 [Warning] 'proxies_priv' entry '@% root@eca312c9edad' ignored in --skip-name-resolve mode.
database_1  | 
database_1  | /usr/local/bin/docker-entrypoint.sh: running /docker-entrypoint-initdb.d/init_cluster_conf.sh
gelarcluster_database_1 exited with code 2

Am i doing wrong? Can i provide some more output to help you fixing the issue?

a node issue could cause to be locked out from the cluster

Hi,
after sometime in wich the cluster runs great (a bit slow, but works), today i found it down (on the logs, the nodes seems that fail to connect between), so i tryied to investigate the problem, but i can't spend much time to debug while many services was down. All that i know is that yesterday i restarted one node. My question is: the cluster is affected of some known issue? What happen if the container that bootstrap the cluster restarts?

Sorry for my english :D

Persistence

I realize the description on the readme states that this is supposed to work with no persistent data volumes, but I really like what you've done with this - I just wanted the extra peace of mind of having data persistence. I'd like to see it added as an option.

I made a version that, sensing a volume at /data, manages the mysql datadir in that location. Except, each container gets it's own subfolder. That way you can have multiple containers on each host. Or all the containers can share a network (nfs) location safely. There is also a cleanup function as containers come and go. I'll put in a pull request.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.