Skip to content
This repository was archived by the owner on Nov 15, 2023. It is now read-only.

Conversation

@skunert
Copy link
Contributor

@skunert skunert commented Nov 23, 2022

This PR removes the following subsystems from the minimal node:

  • Availability-Store (collator node should not store chunks)
  • Availability-Distribution (since we have nothing to store, we do not distribute)
  • Chain-API-Subsystem (This was used by the others)

Originally I was under the impression that we need these for PoV-Recovery, but that is not the case.
We still need to register the chunk fetching protocol, since we send requests for this. Answering was done by
the availability-distribution subsystem, which is now removed. If we receive such a request we always send back NoSuchChunk because we are guaranteed to not have it.

@skunert skunert added B0-silent Changes should not be mentioned in any release notes A0-please_review Pull request needs code review. C1-low PR touches the given topic and has a low impact on builders. labels Nov 23, 2022
@skunert skunert requested a review from a team November 23, 2022 13:16
let (collation_req_receiver, available_data_req_receiver, pov_req_receiver, chunk_req_receiver) =
let (collation_req_receiver, available_data_req_receiver, chunk_req_receiver) =
build_request_response_protocol_receivers(&request_protocol_names, &mut config);
drain_unwanted_request_channels(&task_manager, chunk_req_receiver);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Okay, this is unneeded. We can not do two things. Either we drop this channel or we do not even register the channel.

Comment on lines 245 to 246
let (chunk_req_receiver, cfg) = IncomingRequest::get_config_receiver(request_protocol_names);
config.network.request_response_protocols.push(cfg);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
let (chunk_req_receiver, cfg) = IncomingRequest::get_config_receiver(request_protocol_names);
config.network.request_response_protocols.push(cfg);
let (_, cfg) = IncomingRequest::get_config_receiver(request_protocol_names);
// We don't support inbound requests for this protocol.
let cfg = RequestResponseConfig { inbound_queue: None, ..cfg };
config.network.request_response_protocols.push(cfg);

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should probably support this in Polkadot directly. When it is a collator/full node we should not register an incoming receiver

@skunert
Copy link
Contributor Author

skunert commented Nov 25, 2022

Waiting for paritytech/polkadot#6343, then we can remove the inbound channel.

@bkchr
Copy link
Member

bkchr commented Nov 27, 2022

bot merge

@paritytech-processbot
Copy link

Waiting for commit status.