Record suddenly disappear after a day

Operations
, ,
1

I have namespace “billing_gateway_ns” and have set “company” with 2 record, which have PK. yesterday so far i’m fine manipulates them, but this day it seems cannot view my record. i didn’t understand why it vanished, is it some concept in aerospike data i missed?

I’m viewing using AQL and PHP, using 3 devel servers :

192.168.7.241:3000
192.168.7.242:3000
192.168.7.243:3000

and this is my configuration :

# Aerospike database configuration file for use with systemd.

service {
	paxos-single-replica-limit 1 # Number of nodes where the replica count is automatically reduced to 1.
	proto-fd-max 15000
}

logging {
	console {
		context any info
	}
}

network {
	service {
		address any
		port 3000
	}

	heartbeat {
#		mode multicast
#		multicast-group 192.168.7.241
#		port 9918

		# To use unicast-mesh heartbeats, remove the 3 lines above, and see
		# aerospike_mesh.conf for alternative.
		mode mesh
		address 192.168.7.241
		port 3002 # Heartbeat port for this node.

                # List one or more other nodes, one ip-address & port per line:
		mesh-seed-address-port 192.168.7.241 3002
		mesh-seed-address-port 192.168.7.242 3002
		mesh-seed-address-port 192.168.7.243 3002
#               mesh-seed-address-port 10.10.10.13 3002
#               mesh-seed-address-port 10.10.10.14 3002


		interval 150
		timeout 40
	}

	fabric {
		port 3001
	}

	info {
		port 3003
	}
}

namespace test {
	replication-factor 2
	memory-size 4G
	default-ttl 30d # 30 days, use 0 to never expire/evict.

	storage-engine memory
}

namespace bar {
	replication-factor 2
	memory-size 4G
	default-ttl 30d # 30 days, use 0 to never expire/evict.

	storage-engine memory

	# To use file storage backing, comment out the line above and use the
	# following lines instead.
#	storage-engine device {
#		file /opt/aerospike/data/bar.dat
#		filesize 16G
#		data-in-memory true # Store data in memory in addition to file.
#	}
}

namespace billing_gateway_ns {
	replication-factor 2
	memory-size 4G
	default-ttl 30d # 30 days, use 0 to never expire/evict.

	storage-engine memory
}
2

See that billing_gateway_ns is marked storage-engine memory. Did you restart the Aerospike service (an in-memory data will not be available unless persisted on disk/file).

The only way that data ‘vanishes’ from Aerospike is Expiration, Eviction and Deletion (set-delete, truncate, client delete).

1 Like
3

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