[ https://issues.apache.org/jira/browse/IGNITE-15083?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17908497#comment-17908497 ]
Nikolay Izhikov commented on IGNITE-15083: ------------------------------------------ All failed tests are flaky. TcpDiscoverySpiFailureTimeoutSelfTest.testConnectionCheckMessage - https://ci2.ignite.apache.org/test/1976455332399405407?currentProjectId=IgniteTests24Java8&orderBy=status&order=desc ContinuousQueryTestSuite: TestLongEventsProcessingDisconnect - https://ci2.ignite.apache.org/test/-4232096972891564304?currentProjectId=IgniteTests24Java8 IgniteCacheQueryStopOnCancelOrTimeoutDistributedJoinSelfTest.testTimeout2 - https://ci2.ignite.apache.org/test/-5992755634480521477?currentProjectId=IgniteTests24Java8 IgniteCacheQueryStopOnCancelOrTimeoutDistributedJoinSelfTest.testCancel2 - https://ci2.ignite.apache.org/test/-8172460858110862872?currentProjectId=IgniteTests24Java8 IgniteSpiTestSuite: GridTcpCommunicationInverseConnectionEstablishingTest.testClientSkipsInverseConnectionResponse - https://ci2.ignite.apache.org/test/-2983616410078297078?currentProjectId=IgniteTests24Java8 GridTcpCommunicationInverseConnectionEstablishingTest.testClientSkippingInverseConnResponseIsForciblyFailed - https://ci2.ignite.apache.org/test/-5785184112081658705?currentProjectId=IgniteTests24Java8 > Implement leaseholder selection and failover > -------------------------------------------- > > Key: IGNITE-15083 > URL: https://issues.apache.org/jira/browse/IGNITE-15083 > Project: Ignite > Issue Type: Task > Reporter: Alexey Scherbakov > Priority: Major > Labels: iep-61, ignite-3 > Time Spent: 1h 40m > Remaining Estimate: 0h > > The tx design [1] assumes the presence of leaseholder (stronger form of a > leader) for each partition raft group. > * Leaseholder is used for reads without majority heartbeat > * Leaseholder is used for lock requests processing. > * Only one leaseholder should exists at a time. > * Leaseholders map is stored in metastore (can be discovered by asking group > members in the first approach) > * Tx coordinators are subscribed for leaseholder status updates. > The lease acquisiotion implementation details are open for now [2]. > Jraft includes expiration based leases (similar to yugabyte's), and this > should be enough for the first approach. > [1] https://github.com/apache/ignite-3/tree/main/modules/transactions > [2] Cocroach and tikv use raft log based approach. -- This message was sent by Atlassian Jira (v8.20.10#820010)