# Aerospike Go Client Release 2.2.0 (May 21, 2019)

**URL:** <https://discuss.aerospike.com/t/aerospike-go-client-release-2-2-0-may-21-2019/6263>\
**Category:** Releases (Server, Client & Tools)\
**Created:** [May 22, 2019, 7:19am UTC](https://discuss.aerospike.com/t/aerospike-go-client-release-2-2-0-may-21-2019/6263 "2019-05-22T07:19:19Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![mcoberly](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/mcoberly/32/637_2.png) [@mcoberly](https://discuss.aerospike.com/u/mcoberly)\
**Post date:** [May 22, 2019, 7:19am UTC](https://discuss.aerospike.com/t/aerospike-go-client-release-2-2-0-may-21-2019/6263/1 "2019-05-22T07:19:19Z")

</div>

[Aerospike Go client version 2.2.0](http://www.aerospike.com/download/client/go/notes.html#2.2.0)was released on May 21, 2019.

Fixes and improvements release.

#### Improvements

- Transactions will not count a lack of connection in the node’s connection pool as an iteration anymore.

#### Bug Fixes

- Fixes an issue where an empty connection pool would cause a lock contention that would in turn lead to high CPU load.
- Fixes an issue where in some circumstances connection pool would be depleted of connections.
- Fixes an issue where the replica node would not be selected in case of master-node failure in `Policy.ReplicaPolicy.SEQUENCE` for reads.