You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Vyacheslav Koptilin (Jira)" <ji...@apache.org> on 2024/01/23 10:50:00 UTC

[jira] [Assigned] (IGNITE-21247) Log enhancements for LeaseUpdater

     [ https://issues.apache.org/jira/browse/IGNITE-21247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vyacheslav Koptilin reassigned IGNITE-21247:
--------------------------------------------

    Assignee: Denis Chudov

> Log enhancements for LeaseUpdater
> ---------------------------------
>
>                 Key: IGNITE-21247
>                 URL: https://issues.apache.org/jira/browse/IGNITE-21247
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Denis Chudov
>            Assignee: Denis Chudov
>            Priority: Major
>              Labels: ignite-3
>
> In [https://ci.ignite.apache.org/viewLog.html?buildId=7754161&buildTypeId=ApacheIgnite3xGradle_Test_RunAllTests] , test failure of {{{}org.apache.ignite.internal.raftsnapshot.ItTableRaftSnapshotsTest: leaderFeedsFollowerWithSnapshot{}}}, we see that there are no log messages on replica about lease negotiation, which means that it didn't even started on the placement driver active actor's side.  But the active actor has started before. Log doesn't provide any information about the detail what happened on LeaseUpdater.
> The suggestion is to add logging to know whether some exception happened in {{{}updateLeaseBatchInternal{}}}, or in {{{}LeaseNegotiator#negotiate{}}}, and logging of lease updating statistics (how many groups without leaseholders were detected, how many negotiations are in progress, how many leases are prolonged). 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)