MySQL server has gone away #6294
-
Having issues sometimes with Hasura MySQL. This usually happens after the gql engine and mysql server have been running for a (relatively) long time, eh overnight. Some googling resulted me with an article in mysql docs. I have no idea what I would change with this information though. As far as I understand, expected behaviour is that the mysql client would automatically create a fresh connection Any guidance is appreciated! version: "3.0"
services:
web:
image: wordpress
links:
- mysql
environment:
- WORDPRESS_DB_PASSWORD=supersecret
ports:
- "127.0.0.4:8080:80"
volumes:
- ./wordpress:/var/www/html
mysql:
image: mysql:8.0
environment:
- MYSQL_ROOT_PASSWORD=supersecret
- MYSQL_DATABASE=my-wpdb
volumes:
- mysql:/var/lib/mysql
postgres:
image: postgres:12
restart: always
volumes:
- hasura_mysql:/var/lib/postgresql/data
environment:
POSTGRES_PASSWORD: postgrespassword
graphql-engine:
image: hasura/graphql-engine:pull5655-633f084f
ports:
- "127.0.0.4:8081:8080"
depends_on:
- "postgres"
command:
- graphql-engine
- --mysql-host
- mysql
- --mysql-user
- root
- --mysql-port
- "3306"
- --mysql-dbname
- my-wpdb
- --mysql-password
- supersecret
- serve
restart: always
environment:
HASURA_GRAPHQL_DATABASE_URL: postgres://postgres:postgrespassword@postgres:5432/postgres
## enable the console served by server
HASURA_GRAPHQL_ENABLE_CONSOLE: "true" # set to "false" to disable console
## enable debugging mode. It is recommended to disable this in production
HASURA_GRAPHQL_DEV_MODE: "true"
HASURA_GRAPHQL_ENABLED_LOG_TYPES: startup, http-log, webhook-log, websocket-log, query-log
## uncomment next line to set an admin secret
HASURA_GRAPHQL_ADMIN_SECRET: xxx
volumes:
hasura_mysql:
mysql:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Sorry for the delay in response here. This appears to be related to a connections issue (also discussed in #6006). We will continue to work on it as we move out of preview and towards GA. |
Beta Was this translation helpful? Give feedback.
Sorry for the delay in response here.
This appears to be related to a connections issue (also discussed in #6006). We will continue to work on it as we move out of preview and towards GA.