Get desktop application:
View/edit binary Protocol Buffers messages
A message to track which physical servers are a part of which Anna membership (memory, disk) tier.
The set of all tiers in the system.
The representation the servers comprising an individual tier.
Used in:
The Tier represented by this message -- either MEMORY or DISK.
The list of servers in this tier.
The IP addresses for an individual server -- the private/public IP distinction is specific to EC2-based deployments.
Used in:
The public IP address for a server.
The private IP address for a server.
A message to capture the access frequencies of individual keys for a particular server thread.
A list of all the key access frequencies tracked during this epoch.
A mapping from an individual key to its access count.
Used in:
The key being tracked.
The number of times this key was accessed during this epoch.
A message to track metadata about how large each key in the system is.
The list of key size metadata tuples being reported.
The size metadata for an individual key.
Used in:
The key for which size metadata is being reported.
The size of the above key.
A message that captures the replication factor for an individual key.
Used in:
The name of the key whose replication factor is being changed.
A set of mappings from individual tiers (MEMORY, DISK -- see Tier enum) to the cross-machine replication factor at that tier.
A set of mappings from individual tiers (MEMORY, DISK -- see Tier enum) to the intra-machine replication factor at that tier.
A message representing the replication level for a single key at a single tier.
Used in:
The tier represented by this message.
The replication level at this particular tier for this particular key.
A message to propagate changes to a set of keys' replication factors.
The set of replication factor updates being sent.
A message to capture the periodic reporting of each server thread's local statistics; these are aggregated by the monioring system.
What percentage of the server thread's storage capacity is being consumed.
What percentage of the server thread's compute capacity is being consumed.
The server thread's reporting epoch.
How many key accesses were serviced during this epoch.
An enum representing all the tiers the system supports -- currently, a memory tier and a disk-based tier.
Used in:
,The value for the memory tier.
The value for the disk-based tier.
The value for the routing tier.
Client-generated feedback used for system monitoring and planning.
A unique ID representing each individual client.
Perceived latency across all requests made by this client.
Notifies the monitoring system that the running benchmark has finished.
The perceived throughput across all keys.
Set during the benchmark warm-up phase to tell the monitoring system that it should ignore policy decisions.
Perceived latencies for individual keys.
Observed latency measurements for individual keys.
Used in:
The key for which latency is being reported.
The observed latency for this key.