[IGNITE-17257] Implement Replica server-side logic

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Labels: ignite-3 transaction3_rw
• Epic Link: Ignite 3 transactions
• Assignee: Sergey Uttsel
• Reporter: Alexander Lapin
• Reviewer: Alexander Lapin
• Created: 28/Jun/22 20:56
• Updated: 30/Nov/22 14:31
• Resolved: 15/Aug/22 14:17

Description

For general context please check IGNITE-17252. In addition to client ReplicaService it's required to implement server side logic that will handle actionRequests. Generally speaking all business related logic will be specified in ReplicaListener, Replica or replica server itself should only handle replication-outer action requests and propagate them to ReplicaListener, so that it might be considered as org.apache.ignite.raft.jraft.rpc.impl.IgniteRpcServer / org.apache.ignite.raft.jraft.rpc.impl.ActionRequestProcessor counterpart that handles all business related replication-external requests.

Issue Links

• blocks: IGNITE-17255 Implement ReplicaService
• blocks: IGNITE-17256 Introduce lease-based engine for primary replica stability (primary replica selection and failover)
• blocks: IGNITE-17258 Implement ReplicaListener
• is blocked by: IGNITE-17252 Introduce Replica, ReplicaServer(?), ReplicaService and ReplicaListener interfaces
• links to: GitHub Pull Request #1002
• links to: PR