Get desktop application:
View/edit binary Protocol Buffers messages
`ControlService` provides an interface for internal work with the storage node.
Immediately remove objects from node's local object storage.
Request to drop the objects.
Body of the request message.
Body signature.
Response to request to drop the objects.
Body of the response message.
Body signature.
Dump objects from the shard.
DumpShard request.
Body of dump shard request message.
Body signature.
DumpShard response.
Body of dump shard response message.
Body signature.
EvacuateShard moves all data from one shard to the others.
EvacuateShard request.
EvacuateShard response.
FlushCache moves all data from one shard to the others.
FlushCache request.
FlushCache response.
Performs health check of the storage node.
Health check request.
Body of health check request message.
Body signature.
Health check request.
Body of health check response message.
Body signature.
Returns list that contains information about all objects in a node.
Request to list all objects in the node.
Body of the request message.
Body signature.
ListObjects response.
Body of the response message.
Body signature.
Returns list that contains information about all shards of a node.
Request to list all shards of the node.
Body of the request message.
Body signature.
ListShards response.
Body of the response message.
Body signature.
ObjectStatus requests object status in the storage engine.
ObjectStatus request.
Body of object status request message.
Body signature.
ObjectStatus response.
Body of object status response message.
Body signature.
Restore objects from dump.
RestoreShard request.
Body of restore shard request message.
Body signature.
RestoreShard response.
Body of restore shard response message.
Body signature.
ReviveObject purge all removal marks from all metabases for object.
ReviveObject request.
Body of revive object request message.
Body signature.
ReviveObject response.
Body of revive object response message.
Body signature.
Sets status of the storage node in NeoFS network map.
Set netmap status request.
Body of set netmap status request message.
Body signature.
Set netmap status response.
Body of set netmap status response message.
Body signature.
Sets mode of the shard.
Request to set mode of the shard.
Body of set shard mode request message.
Body signature.
SetShardMode response.
Body of set shard mode response message.
Body signature.
Blobstor component description.
Used in:
Path to the root.
Component type.
Request body structure.
Used in:
List of object addresses to be removed. in NeoFS API binary format.
Response body structure.
Used in:
(message has no fields)
Request body structure.
Used in:
ID of the shard.
Path to the output.
Flag indicating whether object read errors should be ignored.
Response body structure.
Used in:
(message has no fields)
Request body structure.
Used in:
ID of the shard.
Flag indicating whether object read errors should be ignored.
Response body structure.
Used in:
Request body structure.
Used in:
ID of the shard.
Response body structure.
Used in:
(message has no fields)
Health check request body.
Used in:
(message has no fields)
Health check response body
Used in:
Status of the storage node in NeoFS network map.
Health status of storage node application.
Health status of the storage node application.
Used in:
Undefined status, default value.
Storage node application is starting.
Storage node application is started and serves all services.
Storage node application is shutting down.
Request body structure.
Used in:
(message has no fields)
Response body structure.
Used in:
Addresses of the object.
Request body structure.
Used in:
(message has no fields)
Response body structure.
Used in:
List of the node's shards.
Network map structure.
Network map revision number.
Nodes presented in network.
Status of the storage node in the NeoFS network map.
Used in: , ,
Undefined status, default value.
Node is online.
Node is offline.
Node is maintained by the owner.
NeoFS node description.
Used in:
Public key of the NeoFS node in a binary format.
Ways to connect to a node.
Carries list of the NeoFS node attributes in a key-value form. Key name must be a node-unique valid UTF-8 string. Value can't be empty. NodeInfo structures with duplicated attribute names or attributes with empty values will be considered invalid.
Carries state of the NeoFS node.
Administrator-defined Attributes of the NeoFS Storage Node. `Attribute` is a Key-Value metadata pair. Key name must be a valid UTF-8 string. Value can't be empty. Node's attributes are mostly used during Storage Policy evaluation to calculate object's placement and find a set of nodes satisfying policy requirements. There are some "well-known" node attributes common to all the Storage Nodes in the network and used implicitly with default values if not explicitly set: * Capacity \ Total available disk space in Gigabytes. * Price \ Price in GAS tokens for storing one GB of data during one Epoch. In node attributes it's a string presenting floating point number with comma or point delimiter for decimal part. In the Network Map it will be saved as 64-bit unsigned integer representing number of minimal token fractions. * Locode \ Node's geographic location in [UN/LOCODE](https://www.unece.org/cefact/codesfortrade/codes_index.html) format approximated to the nearest point defined in standard. * Country \ Country code in [ISO 3166-1_alpha-2](https://en.wikipedia.org/wiki/ISO_3166-1_alpha-2) format. Calculated automatically from `Locode` attribute * Region \ Country's administrative subdivision where node is located. Calculated automatically from `Locode` attribute based on `SubDiv` field. Presented in [ISO 3166-2](https://en.wikipedia.org/wiki/ISO_3166-2) format. * City \ City, town, village or rural area name where node is located written without diacritics . Calculated automatically from `Locode` attribute. For detailed description of each well-known attribute please see the corresponding section in NeoFS Technical specification.
Used in:
Key of the node attribute.
Value of the node attribute.
Parent keys, if any. For example for `City` it could be `Region` and `Country`.
Request body structure.
Used in:
Requested object.
Response body structure.
Used in:
Engine's shards that know something about an object.
Information about an object from a single shard.
Used in:
String presentation of shard ID.
Shard's storages (metabase, write-cache, FSTree, etc).
Status from a single shard's component.
Used in:
Component identification.
Object's status in a free form (human readable).
Request body structure.
Used in:
ID of the shard.
Path to the output.
Flag indicating whether object read errors should be ignored.
Response body structure.
Used in:
(message has no fields)
Request body structure.
Used in:
Requested object.
Response body structure.
Used in:
Engine's shards in which the object was revived.
Information about of object's revival status from a single shard.
Used in:
String presentation of shard ID.
Object's revival status in a free form (human readable).
Set netmap status request body.
Used in:
New storage node status in NeoFS network map.
Set netmap status response body
Used in:
(message has no fields)
Request body structure.
Used in:
ID of the shard.
Mode that requested to be set.
Flag signifying whether error counter should be set to 0.
Response body structure.
Used in:
(message has no fields)
Shard description.
Used in:
ID of the shard.
Path to shard's metabase.
Shard's blobstor info.
Path to shard's write-cache, empty if disabled.
Work mode of the shard.
Amount of errors occured.
Path to shard's pilorama storage. DEPRECATED.
Work mode of the shard.
Used in: ,
Undefined mode, default value.
Read-write.
Read-only.
Degraded.
DegradedReadOnly.
Signature of some message.
Used in: , , , , , , , , , , , , , , , , , , , , , , ,
Public key used for signing.
Binary signature.