# Percona xtradb cluster Settings **URL:** \ **Category:** Percona XtraDB Cluster 8.x\ **Created:** [May 27, 2026, 11:22am UTC](https://forums.percona.com/t/percona-xtradb-cluster-settings/40841 "2026-05-27T11:22:35Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![pkm2112](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/pkm2112/32/21433_2.png) [@pkm2112](https://forums.percona.com/u/pkm2112)\ **Post date:** [May 27, 2026, 11:22am UTC](https://forums.percona.com/t/percona-xtradb-cluster-settings/40841/1 "2026-05-27T11:22:35Z")
Dear members Request suggestion. Default value of pc.wait\_prim\_timeout is 30S. In a 3 node cluster, if I set it to 180S, will it help in a situation where bootstrap node starts after other 2 cluster members within 3mins Thanx ---
**Author:** ![CTutte](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/ctutte/32/1341_2.png) [@CTutte](https://forums.percona.com/u/CTutte)\ **Post date:** [May 27, 2026, 1:25pm UTC](https://forums.percona.com/t/percona-xtradb-cluster-settings/40841/2 "2026-05-27T13:25:27Z")
Hi! Defaults are usually safe values. 30 seconds should be good enough for most cases If in your setup you need a larger timeout you should override the default in the configuration file through wsrep\_provider options > **[Percona XtraDB Cluster - Index of wsrep\_provider options](https://docs.percona.com/percona-xtradb-cluster/8.0/wsrep-provider-index.html)** > > The following variables can be set and checked in the wsrep\_provider\_options variable. The value of the variable can be changed in the MySQL configuration file, my.cnf, or by setting the variable value in the MySQL client. Regards ---
**Author:** ![matthewb](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/matthewb/32/34_2.png) [@matthewb](https://forums.percona.com/u/matthewb)\ **Post date:** [May 28, 2026, 4:00pm UTC](https://forums.percona.com/t/percona-xtradb-cluster-settings/40841/3 "2026-05-28T16:00:51Z")
> [@pkm2112](#): > > bootstrap node starts after other 2 cluster members If you already have 2 cluster members, then you **should not** have a bootstrap node. Bootstrapping creates a new cluster. If you have 2 nodes running, that is cluster A. Bootstrap node 1, and now you have cluster A and cluster B. If this is an “all down” situation, then yes, increasing the timeout will allow for a longer startup. ---
**Author:** ![pkm2112](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/pkm2112/32/21433_2.png) [@pkm2112](https://forums.percona.com/u/pkm2112)\ **Post date:** [May 29, 2026, 4:44am UTC](https://forums.percona.com/t/percona-xtradb-cluster-settings/40841/4 "2026-05-29T04:44:10Z")
Based on documentation, a node waits 30s for quorum before it continues start up sequence. By default pc.wait\_for\_timeout is set to 30s Lets say, after full outage, SA or DBA didn’t follow correct startup sequence - bootstrap node was not the first to come up. A node with bootstrap set to 0 was started up . My intention is to increase duration to node wait from 30s to 180s So in 180s, I expect bootstrap node to come up. ---
**Author:** ![yunus.uyanik](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/yunus.uyanik/32/19250_2.png) [@yunus.uyanik](https://forums.percona.com/u/yunus.uyanik)\ **Post date:** [June 18, 2026, 6:48am UTC](https://forums.percona.com/t/percona-xtradb-cluster-settings/40841/5 "2026-06-18T06:48:35Z")
You can do this for sure. We are trying to explain that it is more like a fallback/tolerance setting, not the actual recovery procedure. Increasing `pc.wait_prim_timeout` to 180s may help only in a full outage if the correct bootstrap node starts within that time. But the proper recovery is to first identify and bootstrap the most advanced node, meaning the node with `safe_to_bootstrap: 1` or the highest recovered position, then start the others normally.