Major Feature Release
This is a major feature release of the Go client and touches some of the fundamental aspects of the inner workings of it.
We suggest complete testing of your application before using it in production.
Warning
The ProxyClient
in this version supports a feature in Aerospike Server v7.1 that breaks the Batch functionality in Aerospike Cloud as of the date of this release. If you are using that product, you need to use the Aerospike Go Client v7.1.0. We expect the issue to resolve in the near future.
-
New Features
-
[CLIENT-2238] Convert batch calls with just one key per node in sub-batches to batch requests.
If the number keys for a sub-batch to a node is equal to 1, the client will use a direct operation command instead of batch commands to reduce the load on the server. -
[CLIENT-2274] Use constant sized connection buffers and resize the connection buffers over time.
The client would use a single buffer on the connection and would grow it
per demand in case it needed a bigger buffer, but would not shrink it.
This helped with avoiding using buffer pools and the associated
synchronization, but resulted in excessive memory use in case there were a
few large records in the results, even if they were infrequent.
This changeset does the following:
1. Will use a memory pool for large records only. Large records
are defined as records bigger thanaerospike.PoolCutOffBufferSize
.
This is a tiered pool with different buffer sizes. The pool
usessync.Pool
under the cover, releasing unused buffers back to the
runtime.
2. By using biggeraerospike.DefaultBufferSize
values, the user can
imitate the old behavior, so no memory pool is used most of the time.
3. Settingaerospike.MinBufferSize
will prevent the pool using buffer sizes too small,
having to grow them frequently.
4. Buffers are resized every 5 seconds to the median size of buffers used over the previous period,
within the above limits.This change should result in much lower memory use by the client.
-
[CLIENT-2702] Support Client Transaction Metrics. The native client can now track transaction latencies using histograms. Enable using the
Client.EnableMetrics
API.
-
-
Improvements
- [CLIENT-2862] Use default batch policies when the record level batch policy is
nil
. - [CLIENT-2889] Increase grpc
MaxRecvMsgSize
to handle big records for the proxy client. - [CLIENT-2891] Export various batch operation struct fields. Resolves #247.
- Remove dependency on
xrand
sub-package since the native API is fast enough. - Linter Clean up.
WritePolicy.SendKey
documentation, thanks to Rishabh Sairawat- Replaced the deprecated
ioutil.ReadFile
withos.ReadFile
. PR #430, thanks to Swarit Pandey
- [CLIENT-2862] Use default batch policies when the record level batch policy is
-
Fixes
- [CLIENT-2905] Fix inconsistency of handling in-doubt flag in errors.
- [CLIENT-2890] Support
[]MapPair
return in reflection.
This fix supports unmarshalling ordered maps intomap[K]V
and[]MapPair
in the structs.