Skip to content

Wrap up

For the complete documentation index see: llms.txt

All documentation pages available in markdown.

Troubleshoot

If a dispute exists in Aerospike but a support search returns no results in Elasticsearch, check the following.

  • Aerospike does not start or Cross-Datacenter Replication (XDR) does not ship records. Verify the feature-key file, then inspect XDR statistics and Aerospike logs.

    Terminal
    grep -E '^asdb-change-notification[[:space:]]+true$' features.conf
    docker compose exec -T aerospike \
      asinfo -v "get-stats:context=xdr;dc=esDC"
    docker compose logs aerospike | grep -i 'feature.key\|license\|xdr'

    success increases as XDR ships records. If success stays at 0 while in_queue grows, the destination path has not acknowledged the records.

  • The Elasticsearch connector cannot write to Elasticsearch. Check Elasticsearch connector logs and error metrics.

    Terminal
    docker compose logs aerospike-elasticsearch-outbound | tail -n 50
    curl -fsS http://localhost:8902/manage/rest/v1/metrics | grep -io '"[^"]*error[^"]*":{"count":[0-9]*'

    If XDR success increases but _count remains 0, refresh the index and verify its name before checking the Elasticsearch connector logs. A nonzero requests-error or requests-parse-error count means the Elasticsearch connector rejected or failed to process records.

Clean up the tutorial (optional)

  1. Stop and remove the tutorial containers and network. The Compose file does not create persistent volumes, so this removes the tutorial data.

    Terminal
    docker compose down

  2. Delete the project directory when you no longer need the tutorial. Verify that it contains no files you want to keep, including the sensitive features.conf file.

    Terminal
    cd ..
    rm -rf aerospike-elastic-quickstart