upgrade mariadb version 43/46343/1
authorJorge Hernandez <jh1730@att.com>
Mon, 7 May 2018 04:03:13 +0000 (23:03 -0500)
committerJorge Hernandez <jh1730@att.com>
Mon, 7 May 2018 04:03:13 +0000 (23:03 -0500)
this was an exercise to see if it helps with
the pessimistic lock exceptions on PE side.
The problem still persists, in any case,
the database was outdated, and better to
run with a more up to date one.

Change-Id: I8e51617fde6c1ac9870d1680ebe81e039a333489
Issue-ID: POLICY-777
Signed-off-by: Jorge Hernandez <jh1730@att.com>
docker-compose-integration.yml
docker-compose.yml

index 53b592a..e67729e 100644 (file)
 version: '2'
 services:
    mariadb:
-      image: mariadb:10.0.34
+      image: mariadb:10.2.14
       container_name: mariadb
       hostname: mariadb
-      command: ['--lower-case-table-names=1']
+      command: ['--lower-case-table-names=1', '--wait_timeout=28800']
       env_file: config/db/db.conf
       volumes:
          - ./config/db:/docker-entrypoint-initdb.d
index 18e0ebd..c469755 100644 (file)
@@ -19,10 +19,10 @@ networks:
       com.docker.network.driver.mtu: ${MTU}
 services:
    mariadb:
-      image: mariadb:10.0.34
+      image: mariadb:10.2.14
       container_name: mariadb
       hostname: mariadb
-      command: ['--lower-case-table-names=1']
+      command: ['--lower-case-table-names=1', '--wait_timeout=28800']
       env_file: config/db/db.conf
       volumes:
          - ./config/db:/docker-entrypoint-initdb.d