[jira] [Updated] (IGNITE-17221) Need to propagate HLC with RAFT events
[ https://issues.apache.org/jira/browse/IGNITE-17221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-17221: --- Description: RAFT events help to synchronize HLC between RAFT replicas. All RAFT communications are initiated by a leader, and only one leader can exist at a time. This enforces monotonic growth of HLC on raft group replicas. Heartbeat AppendEntries RPC calls are enriched with sender’s HLC. The HLC update rules are applied on receiving messages. (was: RAFT events help to synchronize HLC between RAFT replicas. All RAFT communications are initiated by a leader, and only one leader can exist at a time. This enforces monotonic growth of HLC on raft group replicas. RequestVote and AppendEntries RPC calls are enriched with sender’s HLC. The HLC update rules are applied on receiving messages.) > Need to propagate HLC with RAFT events > -- > > Key: IGNITE-17221 > URL: https://issues.apache.org/jira/browse/IGNITE-17221 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3, transaction3_ro > > RAFT events help to synchronize HLC between RAFT replicas. All RAFT > communications are initiated by a leader, and only one leader can exist at a > time. This enforces monotonic growth of HLC on raft group replicas. Heartbeat > AppendEntries RPC calls are enriched with sender’s HLC. The HLC update rules > are applied on receiving messages. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17221) Need to propagate HLC with RAFT events
[ https://issues.apache.org/jira/browse/IGNITE-17221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-17221: --- Description: RAFT events help to synchronize HLC between RAFT replicas. All RAFT communications are initiated by a leader, and only one leader can exist at a time. This enforces monotonic growth of HLC on raft group replicas. RequestVote and AppendEntries RPC calls are enriched with sender’s HLC. The HLC update rules are applied on receiving messages. (was: RAFT events help to synchronize HLC between RAFT replicas. All RAFT communications are initiated by a leader, and only one leader can exist at a time. This enforces monotonic growth of HLC on raft group replicas. RequestVote and AppendEntries RPC calls are enriched with sender’s HLC. The HLC update rules are applied on receiving messages. RAFT lease intervals are bound to the HLC range.) > Need to propagate HLC with RAFT events > -- > > Key: IGNITE-17221 > URL: https://issues.apache.org/jira/browse/IGNITE-17221 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3, transaction3_ro > > RAFT events help to synchronize HLC between RAFT replicas. All RAFT > communications are initiated by a leader, and only one leader can exist at a > time. This enforces monotonic growth of HLC on raft group replicas. > RequestVote and AppendEntries RPC calls are enriched with sender’s HLC. The > HLC update rules are applied on receiving messages. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-17221) Need to propagate HLC with RAFT events
Title: Message Title Alexander Lapin updated an issue Ignite / IGNITE-17221 Need to propagate HLC with RAFT events Change By: Alexander Lapin Labels: ignite-3 transaction3_ro Add Comment This message was sent by Atlassian Jira (v8.20.10#820010-sha1:ace47f9)
[jira] [Updated] (IGNITE-17221) Need to propagate HLC with RAFT events
[ https://issues.apache.org/jira/browse/IGNITE-17221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-17221: - Ignite Flags: (was: Docs Required,Release Notes Required) > Need to propagate HLC with RAFT events > -- > > Key: IGNITE-17221 > URL: https://issues.apache.org/jira/browse/IGNITE-17221 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > > RAFT events help to synchronize HLC between RAFT replicas. All RAFT > communications are initiated by a leader, and only one leader can exist at a > time. This enforces monotonic growth of HLC on raft group replicas. > RequestVote and AppendEntries RPC calls are enriched with sender’s HLC. The > HLC update rules are applied on receiving messages. RAFT lease intervals are > bound to the HLC range. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17221) Need to propagate HLC with RAFT events
[ https://issues.apache.org/jira/browse/IGNITE-17221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-17221: - Epic Link: IGNITE-15081 > Need to propagate HLC with RAFT events > -- > > Key: IGNITE-17221 > URL: https://issues.apache.org/jira/browse/IGNITE-17221 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > > RAFT events help to synchronize HLC between RAFT replicas. All RAFT > communications are initiated by a leader, and only one leader can exist at a > time. This enforces monotonic growth of HLC on raft group replicas. > RequestVote and AppendEntries RPC calls are enriched with sender’s HLC. The > HLC update rules are applied on receiving messages. RAFT lease intervals are > bound to the HLC range. -- This message was sent by Atlassian Jira (v8.20.7#820007)
[jira] [Updated] (IGNITE-17221) Need to propagate HLC with RAFT events
[ https://issues.apache.org/jira/browse/IGNITE-17221?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sergey Uttsel updated IGNITE-17221: --- Issue Type: Improvement (was: Task) > Need to propagate HLC with RAFT events > -- > > Key: IGNITE-17221 > URL: https://issues.apache.org/jira/browse/IGNITE-17221 > Project: Ignite > Issue Type: Improvement >Reporter: Sergey Uttsel >Assignee: Sergey Uttsel >Priority: Major > Labels: ignite-3 > > RAFT events help to synchronize HLC between RAFT replicas. All RAFT > communications are initiated by a leader, and only one leader can exist at a > time. This enforces monotonic growth of HLC on raft group replicas. > RequestVote and AppendEntries RPC calls are enriched with sender’s HLC. The > HLC update rules are applied on receiving messages. RAFT lease intervals are > bound to the HLC range. -- This message was sent by Atlassian Jira (v8.20.7#820007)
