maria-discuss team mailing list archive
Mailing list archive
Re: Mariadb 10.1.6, total cluster recovery - gvwstate.dat
Not as far as I am aware, and I would assume there are very good reasons for that. (data consistency, preventing split-brain etc.)
If all 3 nodes are offline (gracefully), and you want to bring one up without editing my.cnf, you should use
or "service mysql bootstrap" depends on what you are using.
..which effectively starts the cluster with wsrep_cluster_address=gcomm://. You will then not need to edit the config file at all.
Of course, when you are killing mysqld on all 3 nodes, you are doing all 3 at the same time so there is little risk of problems. If the nodes were network-partitioned for some period of time and had different data, you probably would not want the cluster to automatically be brought back online, instead manually controlled by you depending on which node is "most correct".
From: Max Zulio [zulioexpress@xxxxxxxxx]
Sent: 19 August 2015 17:40
To: Jamie Gibbard
Subject: Re: [Maria-discuss] Mariadb 10.1.6, total cluster recovery - gvwstate.dat
If I kill -9 mysqld on all three of my nodes in the cluster, then start the services simultaneously,the cluster comes back online successfully using the gvwstate.dat file.
If I gracefully shutdown mysql on all three nodes as you mentioned the gvwstate.dat file is deleted. This means when the cluster needs to be restarted I am forced to edit my.cnf and replace wsrep_cluster_address=gcomm://x.x.x.x,y.y.y.y,z.z.z.z with wsrep_cluster_address=gcomm:// on one of the nodes before I can bring up the cluster.
Is there anyway to have the last node that is shutdown gracefully keep it's gvwstate.dat file so that the next time the cluster is started it can come online without editing the config file?
On Thu, Aug 13, 2015 at 1:34 PM, Jamie Gibbard <Jamie.Gibbard@xxxxxxxxxxxx<mailto:Jamie.Gibbard@xxxxxxxxxxxx>> wrote:
Are you sure there are no other errors? I'm not sure that the file being missing is the problem there:
When a node stores the Primary Component state to disk, it saves it as the gvwstate.dat file. The node creates and updates this file when the cluster forms or changes the Primary Component. This ensures that the node retains the latest Primary Component state that it was in. If the node loses connectivity, it has the file to reference. If the node shuts down gracefully, it deletes the file.
You might want to paste the full log exert into a Pastie style website, give a fuller description about the node restart (for instance, were you expecting an IST? an SST? Do the nodes form a cluster at all? etc etc ). That would probably be helpful to someone willing to assist.
From: Maria-discuss [maria-discuss-bounces+jamie.gibbard=netnames.com@xxxxxxxxxxxxxxxxxxx<mailto:netnames.com@xxxxxxxxxxxxxxxxxxx>] on behalf of Max Zulio [zulioexpress@xxxxxxxxx<mailto:zulioexpress@xxxxxxxxx>]
Sent: 13 August 2015 12:17
Subject: [Maria-discuss] Mariadb 10.1.6, total cluster recovery - gvwstate.dat
I am using a Mariadb 10.1.6 three node cluster with wsrep. There is a gvwstate.dat file created in /var/lib/mysql, but in the log file when restarting the nodes I see: [Warning] WSREP: access file(gvwstate.dat) failed(No such file or directory).
This seems to be the only thing stopping automatic cluster recovery. Where is mariadb looking for the file, or is there a way of configuring the file location?
NetNames, 25 Canada Square, Canary Wharf, London E14 5LQ, UK | Tel: +44 207 015 9200<tel:%2B44%20207%20015%209200> | NetNames Limited, Registered in England and Wales, Company number: 3169594, VAT Number: GB 739633893
NetNames, 25 Canada Square, Canary Wharf, London E14 5LQ, UK | Tel: +44 207 015 9200 | NetNames Limited, Registered in England and Wales, Company number: 3169594, VAT Number: GB 739633893