The Aerospike Standup Vol. 10

Happy August! We’re happy to have everyone on this edition of the Aerospike Standup, a newsletter written by developers for developers. As always you will find here blog posts, questions from the community, documentation, releases and events, written by the Aerospike team. This volume we’re celebrating the release of v5.1!

We’ll be sharing this newsletter with updates every other week. If you want to get updates to your email, click here to subscribe.

Questions From the Community

• Can’t connect to aerospike-server in docker-compose.yml

• Map/List Operations

• How to get Key from Query Records

• Get node/cluster name from INFO_NODE

• Effect of Availability if going with Strong Consistency

• How to Restore Aerospike from Incremental Backup file

• Disable specific TLS cipher suits in Aerospike server configuration

New Articles

• Aerospike Database 5.1: Security Enhancements including HashiCorp Vault Integration, Paul Jensen VP of Engineering Operations, Aerospike

• Authentication and Authorization using Aerospike REST Client, Eugene R.

• Aerospike on EKS (AWS K8s), dev.to, Ken Tune, Solution Architect, Aerospike

• Ansible for Aerospike, dev.to, Ken Tune, Solution Architect, Aerospike

Release Notes

• July 19:

  • REST Client

    v1.6.0

• July 20

  • C# Client

    v3.9.8

• July 27

  • REST Client

    v1.6.1

  • Prometheus Exporter

    1.1.0

• July 30

  • Rust Client

    v0.5.0

• July 31

  • Server EE

    5.1.0.3

  • Server CE

    5.1.0.3

  • Tools

    v3.29.0

New/Updated Documentation

• Optional integration for Hashicorp Vault

  https://docs.aerospike.com/operations/configure/security/vault/index.html

• New or changed XDR configuration parameters and metrics:

  • period-ms governs the length of cycling through the XDR transaction queue.

  • write-policy is one of auto (default), update, or replace. “auto” and “update” accommodate on bin shipping.

  • compression-level controls the amount of compression applied to data-in-transit to remote destinations. Must be accompanied by

    enable-compression true

  • sc-replication-wait-ms is the time to wait between replications in the transaction queue to allow client writes to finish actual replication when Strong Consistency is enabled.

  • retry_no_node metric tracks when a node at the destination cannot be found.

• Other configuration parameter changes:

• Default for parameter proto-fd-idle-ms is now 0.

• New parameter microsecond-histograms allows finer granularity on histograms.

Upcoming Events

• Kafka Summit 2020

  – Sponsored Session – Distributed Data Storage & Streaming for Real-time Decisioning using Kafka, Spark and Aerospike. Aug 24, 11:30AM PDT

• Enterprise Database Strategies for 2020

  – An Examination of IT Data Management Trends and How the Industry Responds, Webinar: Live online Aug 27, 2020, 10 AM PT / 1 PM ET