What's the difference between objects on "Master" and "Prole"?

1 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~Namespace Object Information (2024-07-17 01:50:02 UTC)~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Namespace|            Node|Rack|  Repl|Expirations|   Total|~~~~~~~~~~~Objects~~~~~~~~~~~|~~~~~~~~~Tombstones~~~~~~~~|~~~~Pending~~~~
         |                |  ID|Factor|           | Records|  Master|   Prole|Non-Replica| Master|  Prole|Non-Replica|~~~~Migrates~~~
         |                |    |      |           |        |        |        |           |       |       |           |     Tx|     Rx
test_125 |125:3000        |   0|     2|    0.000  | 0.000  | 0.000  | 0.000  |    0.000  |0.000  |0.000  |    0.000  |0.000  |0.000
test_125 |testpc11839:3000|   0|     2|    0.000  | 0.000  | 0.000  | 0.000  |    0.000  |0.000  |0.000  |    0.000  |0.000  |0.000
test_125 |                |    |      |    0.000  | 0.000  | 0.000  | 0.000  |    0.000  |0.000  |0.000  |    0.000  |0.000  |0.000
test_39  |125:3000        |   0|     2|    0.000  |10.000  |10.000  | 0.000  |    0.000  |0.000  |0.000  |    0.000  |0.000  |0.000
test_39  |testpc11839:3000|   0|     2|    0.000  |25.000  |15.000  |10.000  |    0.000  |0.000  |0.000  |    0.000  |0.000  |0.000
test_39  |                |    |      |    0.000  |35.000  |25.000  |10.000  |    0.000  |0.000  |0.000  |    0.000  |0.000  |0.000
Number of rows: 4
  1. What does “Prole” mean? Does “Master” mean the objects which are stored on master node?
  2. How does Aerospike separate object to “Master” or “Prole”? Is there a rule to do this?
2

The server records “master”, “prole”, and “non_replica” metrics for “objects” and “tombstones”. These are documented in the metrics reference.

The master/prole are analogous to primary/secondary or leader/follower in other systems. Master objects indicate the number of records which this node is able to accept writes for. Prole objects indicate the number of records which this node is a replica to a master - it can receive reads from the client, but can’t receive writes. Non-replica objects are objects that are neither master or prole which can’t be read or written to. Non-replica objects are held to maintain the replication-factor while data is migrating between the current replicas (master and proles).

See data distribution docs.