# Identify the XDR settings applied to the cluster

**URL:** <https://discuss.aerospike.com/t/identify-the-xdr-settings-applied-to-the-cluster/8645>\
**Category:** Configuration\
**Tags:** xdr\
**Created:** [July 20, 2021, 4:44am UTC](https://discuss.aerospike.com/t/identify-the-xdr-settings-applied-to-the-cluster/8645 "2021-07-20T04:44:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![shan.p](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/shan.p/32/1990_2.png) [@shan.p](https://discuss.aerospike.com/u/shan.p)\
**Post date:** [July 20, 2021, 4:44am UTC](https://discuss.aerospike.com/t/identify-the-xdr-settings-applied-to-the-cluster/8645/1 "2021-07-20T04:44:00Z")

</div>

I have to identify the XDR settings of a cluster, which is spun up using Ansible playbook and may have a dynamic XDR configuration applied.

Is there a way to identify the XDR settings applied to a cluster?

I tried the following command and can see that the XDR is enabled.

```auto
asinfo -v "get-config:context=xdr";

```

This shows that XDR is enabled and other parameters. However is there a way to find the dc-node-addresses setup for XDR?

---

<div class="post-metadata">

**Author:** ![neelp](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/neelp/32/1369_2.png) [@neelp](https://discuss.aerospike.com/u/neelp)\
**Post date:** [July 23, 2021, 5:23am UTC](https://discuss.aerospike.com/t/identify-the-xdr-settings-applied-to-the-cluster/8645/2 "2021-07-23T05:23:50Z")

</div>

You can use this command to get the remote DC seed nodes: asinfo -v “get-config:context=xdr;dc=DC1”

---

<div class="post-metadata">

**Author:** ![shan.p](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/shan.p/32/1990_2.png) [@shan.p](https://discuss.aerospike.com/u/shan.p)\
**Post date:** [July 26, 2021, 7:12pm UTC](https://discuss.aerospike.com/t/identify-the-xdr-settings-applied-to-the-cluster/8645/3 "2021-07-26T19:12:55Z")

</div>

@neelp I get the following output.

```auto
$ asinfo -v 'get-config:context=xdr;dc=dc1'
enable-xdr=false;enable-change-notification=false;forward-xdr-writes=false;xdr-delete-shipping-enabled=true;
xdr-nsup-deletes-enabled=false;xdr-shipping-enabled=true;xdr-ship-bins=false;xdr-write-timeout=10000;xdr-client-threads=3;xdr-max-ship-throughput=0;
xdr-max-ship-bandwidth=0;xdr-hotkey-time-ms=100;xdr-read-threads=4;xdr-info-timeout=10000;xdr-compression-threshold=0;xdr-digestlog-iowait-ms=500;xdr-digestlog-size=0;\xdr-min-digestlog-free-pct=0;xdr-digestlog-path=NULL

```

Does this indicate that the XDR is setup as just a placeholder, and there are no nodes for replication?

---

<div class="post-metadata">

**Author:** ![meher](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/meher/32/1644_2.png) [@meher](https://discuss.aerospike.com/u/meher)\
**Post date:** [July 26, 2021, 11:44pm UTC](https://discuss.aerospike.com/t/identify-the-xdr-settings-applied-to-the-cluster/8645/4 "2021-07-26T23:44:52Z")

</div>

I think that for the older XDR (this seems to be a 4.X XDR configuration), the [`get-dc-config`](https://docs.aerospike.com/docs/reference/info/?show-removed=1#get-dc-config) command would be what you are looking for. As XDR is an Enterprise feature, you should be able to have someone on your side reach out to Aerospike Support as well.

---

<div class="post-metadata">

**Author:** ![system](https://sea1.discourse-cdn.com/flex019/user_avatar/discuss.aerospike.com/system/32/2274_2.png) [@system](https://discuss.aerospike.com/u/system)\
**Post date:** [October 18, 2021, 11:45pm UTC](https://discuss.aerospike.com/t/identify-the-xdr-settings-applied-to-the-cluster/8645/5 "2021-10-18T23:45:36Z")

</div>

This topic was automatically closed 84 days after the last reply. New replies are no longer allowed.