RATIS-2509. Introduce local read API to reduce serde cost

[ivandika3]

What changes were proposed in this pull request?

See https://issues.apache.org/jira/browse/RATIS-2509

OM code integration

    public OMResponse submitReadRequest(OMRequest omRequest, Function<OMRequest, OMResponse> handler)
      throws ServiceException {
    try {
      return serverDivision.readOnlyAsync(() -> CompletableFuture.completedFuture(handler.apply(omRequest))).get();
    } catch (ExecutionException | IOException ex) {
      throw new ServiceException(ex.getMessage(), ex);
    } catch (InterruptedException ex) {
      Thread.currentThread().interrupt();
      throw new ServiceException(ex.getMessage(), ex);
    }

  }

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/RATIS-2509

How was this patch tested?

OM Leader read performance testing, the Ratis read performance is on par with the direct read.

• Before patch: 235020 QPS -> 180433 QPS (24% QPS reduction)
• After patch: 235020 QPS -> 228362 (3% QPS reduction)

(Putting this to draft since my GH account is currently blocked from GH actions).

[szetszwo]

@ivandika3 , thanks for working on this! Please see the comments inlined and also https://issues.apache.org/jira/secure/attachment/13082106/1448_review.patch

[szetszwo]

• Since the query method in StateMachine does not throw IOException, let's just use Supplier here. It will force the StateMachine to handle IOException, if there is any.

//StateMachine
  CompletableFuture<Message> query(Message request);

• Also, we need clientId and readRequestType to support read-after-write-consistency.

    default <T> CompletableFuture<T> readOnlyAsync(ClientId clientId, ReadRequestTypeProto readRequestType,
        Supplier<CompletableFuture<T>> query) throws IOException {

[ivandika3]

Good point, updated.