Node information request is missing in v2.0 API #17

New issue

Closed

opened 2025-12-28 18:11:54 +00:00 by sami · 2 comments

sami commented

2025-12-28 18:11:54 +00:00

Owner

Originally created by @realloc on GitHub (Aug 26, 2020).

Originally assigned to: @realloc on GitHub.

There is need to check if node is ready to serve requests and get basic information about it. Previously this functionality was in Healthcheck service.

We need to add some simple ping-pong functionality without implementation specifics. It could be NodeInfo structure request in netmap service.

Originally created by @realloc on GitHub (Aug 26, 2020). Originally assigned to: @realloc on GitHub. There is need to check if node is ready to serve requests and get basic information about it. Previously this functionality was in `Healthcheck` service. We need to add some simple ping-pong functionality without implementation specifics. It could be `NodeInfo` structure request in `netmap` service.

sami

2025-12-28 18:11:54 +00:00

closed this issue
added the
bug

discussion
labels

sami commented

2025-12-28 18:11:55 +00:00

Author

Owner

@realloc commented on GitHub (Sep 2, 2020):

I propose to add an rpc call to Netmap Service, that would provide only state of the node for ping-pong-like cases and full NodeInfo for updating nodes' local netmap view.

// Request to get NodeInfo from the particular node directly, not by just
// reading it from Netmap.
message LocalNodeInfoRequest {
  //Request body
  message Body {
    // Return only node State, not full NodeInfo message
    bool status_only = 1;
  }
  // Body of the balance request message.
  Body body = 1;

  // Carries request meta information. Header data is used only to regulate
  // message transport and does not affect request execution.
  neo.fs.v2.session.RequestMetaHeader meta_header = 2;

  // Carries request verification information. This header is used to
  // authenticate the nodes of the message route and check the correctness
  // of transmission.
  neo.fs.v2.session.RequestVerificationHeader verify_header = 3;
}

@realloc commented on GitHub (Sep 2, 2020): I propose to add an rpc call to Netmap Service, that would provide only state of the node for ping-pong-like cases and full NodeInfo for updating nodes' local netmap view. ```protobuf // Request to get NodeInfo from the particular node directly, not by just // reading it from Netmap. message LocalNodeInfoRequest { //Request body message Body { // Return only node State, not full NodeInfo message bool status_only = 1; } // Body of the balance request message. Body body = 1; // Carries request meta information. Header data is used only to regulate // message transport and does not affect request execution. neo.fs.v2.session.RequestMetaHeader meta_header = 2; // Carries request verification information. This header is used to // authenticate the nodes of the message route and check the correctness // of transmission. neo.fs.v2.session.RequestVerificationHeader verify_header = 3; } ```

sami commented

2025-12-28 18:11:56 +00:00

Author

Owner

@alexvanin commented on GitHub (Sep 2, 2020):

@realloc I don't mind to have this service in API, but node definitely should implement more specific health check services. How response will look like?

@alexvanin commented on GitHub (Sep 2, 2020): @realloc I don't mind to have this service in API, but node definitely should implement more specific health check services. How response will look like?