# Docker Entrypoint percona-xtradb-cluster-8.0 - Timeout on update **URL:** https://forums.percona.com/t/docker-entrypoint-percona-xtradb-cluster-8-0-timeout-on-update/30842 **Category:** Percona XtraDB Cluster 8.x **Tags:** closed-no-reply **Created:** [June 6, 2024, 8:38am UTC](https://forums.percona.com/t/docker-entrypoint-percona-xtradb-cluster-8-0-timeout-on-update/30842 "2024-06-06T08:38:47Z") **Posts on this page:** 1 **Page:** 1
### Author: ![Daniel\_Wilhelm](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/daniel_wilhelm/32/16786_2.png) [@Daniel\_Wilhelm](https://forums.percona.com/u/Daniel_Wilhelm) #### Post date: [June 6, 2024, 8:38am UTC](https://forums.percona.com/t/docker-entrypoint-percona-xtradb-cluster-8-0-timeout-on-update/30842/1 "2024-06-06T08:38:48Z")
hi, we are trying to upgrade our cluster from .29 to .36. The old entrypoint script in .29 only did the init checks if the datadir is empty whereas the new one also compares the versions. In our case this leads to triggering the 120s timeout here: [percona-docker/percona-xtradb-cluster-8.0/dockerdir/entrypoint.sh at main · percona/percona-docker · GitHub](https://github.com/percona/percona-docker/blob/main/percona-xtradb-cluster-8.0/dockerdir/entrypoint.sh#L222) As our cluster is quite large with 1,3 TB data the startup takes some time and i wondered what the reasons behind this change were. I understand it if we start a new instance that we can predict the time it should take but with a version upgrade the time is probably very different depending on the scenario. This leads to a full stop of the mysql process while in the upgrade procedure of the underlying databases. Or am i missing a changed procedure for doing the upgrade with tthe container version? Couldn’t find any infos on this topic in the readme. Our update strategy was to do a maintenance perdiod, stop the whole cluster, update the bootstrap node and join the other nodes (with a new version using a full sst). Thanks Daniel