[jira] [Updated] (IGNITE-20918) Leases expire after a node has been restarted
[ https://issues.apache.org/jira/browse/IGNITE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alexander Lapin updated IGNITE-20918: - Release Note: (was: Was fixed in other issues, where nodeId matching check was added. Mainly https://issues.apache.org/jira/browse/IGNITE-20883.) > Leases expire after a node has been restarted > - > > Key: IGNITE-20918 > URL: https://issues.apache.org/jira/browse/IGNITE-20918 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtcev >Assignee: Alexander Lapin >Priority: Critical > Labels: ignite-3 > Time Spent: 1h 40m > Remaining Estimate: 0h > > IGNITE-20910 introduces a test that inserts some data after restarting a > node. For some reason, after some time, I can see the following messages in > the log: > {noformat} > [2023-11-22T10:00:17,056][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_19] > [2023-11-22T10:00:17,057][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_0] > [2023-11-22T10:00:17,057][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_9] > [2023-11-22T10:00:17,057][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_10] > {noformat} > After that, the test fails with a {{PrimaryReplicaMissException}}. The > problem here, that it is expected that a single node should never have > expired leases, they should be prolongated automatically. I think that this > happens because the initial lease that was issued before the node was > restarted is still accepted by the node after restart. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20918) Leases expire after a node has been restarted
[ https://issues.apache.org/jira/browse/IGNITE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vyacheslav Koptilin updated IGNITE-20918: - Epic Link: IGNITE-21389 > Leases expire after a node has been restarted > - > > Key: IGNITE-20918 > URL: https://issues.apache.org/jira/browse/IGNITE-20918 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtcev >Assignee: Alexander Lapin >Priority: Critical > Labels: ignite-3 > Time Spent: 1.5h > Remaining Estimate: 0h > > IGNITE-20910 introduces a test that inserts some data after restarting a > node. For some reason, after some time, I can see the following messages in > the log: > {noformat} > [2023-11-22T10:00:17,056][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_19] > [2023-11-22T10:00:17,057][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_0] > [2023-11-22T10:00:17,057][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_9] > [2023-11-22T10:00:17,057][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_10] > {noformat} > After that, the test fails with a {{PrimaryReplicaMissException}}. The > problem here, that it is expected that a single node should never have > expired leases, they should be prolongated automatically. I think that this > happens because the initial lease that was issued before the node was > restarted is still accepted by the node after restart. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (IGNITE-20918) Leases expire after a node has been restarted
[ https://issues.apache.org/jira/browse/IGNITE-20918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aleksandr Polovtcev updated IGNITE-20918: - Description: IGNITE-20910 introduces a test that inserts some data after restarting a node. For some reason, after some time, I can see the following messages in the log: {noformat} [2023-11-22T10:00:17,056][INFO ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] Primary replica expired [grp=5_part_19] [2023-11-22T10:00:17,057][INFO ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] Primary replica expired [grp=5_part_0] [2023-11-22T10:00:17,057][INFO ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] Primary replica expired [grp=5_part_9] [2023-11-22T10:00:17,057][INFO ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] Primary replica expired [grp=5_part_10] {noformat} After that, the test fails with a {{PrimaryReplicaMissException}}. The problem here, that it is expected that a single node should never have expired leases, they should be prolongated automatically. I think that this happens because the initial lease that was issued before the node was restarted is still accepted by the node after restart. > Leases expire after a node has been restarted > - > > Key: IGNITE-20918 > URL: https://issues.apache.org/jira/browse/IGNITE-20918 > Project: Ignite > Issue Type: Bug >Reporter: Aleksandr Polovtcev >Priority: Critical > Labels: ignite-3 > > IGNITE-20910 introduces a test that inserts some data after restarting a > node. For some reason, after some time, I can see the following messages in > the log: > {noformat} > [2023-11-22T10:00:17,056][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_19] > [2023-11-22T10:00:17,057][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_0] > [2023-11-22T10:00:17,057][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_9] > [2023-11-22T10:00:17,057][INFO > ][%isnt_tmpar_0%metastorage-watch-executor-3][PartitionReplicaListener] > Primary replica expired [grp=5_part_10] > {noformat} > After that, the test fails with a {{PrimaryReplicaMissException}}. The > problem here, that it is expected that a single node should never have > expired leases, they should be prolongated automatically. I think that this > happens because the initial lease that was issued before the node was > restarted is still accepted by the node after restart. -- This message was sent by Atlassian Jira (v8.20.10#820010)