Shadow file do not works as expected

aerospike version: 3.15.1.4

configure:

# Aerospike database configuration file.

# This stanza must come first.
service {
  user admin
  group admin
  paxos-single-replica-limit 1 # Number of nodes where the replica count is automatically reduced to 1.
  pidfile /home/admin/aerospike/var/run/aerospike.pid
  proto-fd-max 15000
  work-directory /home/admin/aerospike/var
  migrate-threads 4
  log-local-time true
}

logging {
  # Log file must be an absolute path.
  file /home/admin/aerospike/var/log/aerospike.log {
    context any info
  }
}

mod-lua {
  system-path /home/admin/aerospike/share/udf/lua
  user-path /home/admin/aerospike/var/udf/lua
}

network {
  service {
    address any
    port 3000
  }

heartbeat {
    mode mesh
    address eth0
    port 3002
    interval  150
    timeout 10
    mesh-seed-address-port 192.168.129.99 3002
  }

  fabric {
    port 3001
  }

  info {
    port 3003
  }
}

namespace ns1 {
    replication-factor 2
    memory-size 2G
    default-ttl 90d
    high-water-memory-pct 70
    high-water-disk-pct 60
    evict-tenths-pct 10
    storage-engine device {
            file /home/admin/aerospike/data/test.dat /home/admin/aerospike/data2/test2.dat
            filesize 4G
            data-in-memory true
            write-block-size 256K
        }
}

when I start server and write some data, I only can see the test.data file in /home/admin/aerospike/data, but the shadow file test2.dat do not exist in /home/admin/aerospike/data2.

Is there something some wrong?

From Configuration Reference | Aerospike Documentation :

Data file path on rotational disk (using a file system) or pemem (as of version 4.8). As of 4.3.0.2, the file may include an optional ‘shadow file’ as a second argument.

Shadow files were not supported until 4.3.0.2.