# recovery issues (IST\\SST) on Docker

**URL:** <https://forums.percona.com/t/recovery-issues-ist-sst-on-docker/5165>\
**Category:** Percona XtraDB Cluster 5.x\
**Created:** [October 24, 2016, 9:40am UTC](https://forums.percona.com/t/recovery-issues-ist-sst-on-docker/5165 "2016-10-24T09:40:59Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Joe\_Levi](https://avatars.discourse-cdn.com/v4/letter/j/e0b2c6/32.png) [@Joe\_Levi](https://forums.percona.com/u/Joe_Levi)\
**Post date:** [October 24, 2016, 9:40am UTC](https://forums.percona.com/t/recovery-issues-ist-sst-on-docker/5165/1 "2016-10-24T09:40:59Z")

</div>

Hey Guys,

I have this issue with the xtraDB Cluster set on a docker cluster.  
Got a 3 nodes cluster set up on 3 different docker engine machines.  
The cluster is working fine. and whilst the DB is pretty small now it’s gonna grow.

I started running fail/recovery tests knowing that there’s an automated system in PCX that logs the last GID for IST recovery.  
but, every time I restart the node it gets a -1 GID and runs a full SST.

As far as I know the gchache.size is big enough to hold the needed transactions for the IST.

Anyone got an idea why the IST doesn’t kick into action?