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

Vladislav Pyatkov updated IGNITE-20485:
---------------------------------------
    Description: 
*Motivation*
Currently, the lease interval depends on the lease update frequency and is 
calculated like this:
{code:title=LeaseUpdater.java}
private static final long LEASE_INTERVAL = 10 * UPDATE_LEASE_MS;
{code}
The interval is impossible to configure; that way, it makes the test longer 
than it can be with a short lease interval.

*Implementation notes*

* Create a new property root to configure. The property has to be specified for 
the placement driver only (PlacementDriverConfigurationScema).
* The property should be configured for the entire cluster 
(ConfigurationType#DISTRIBUTED).
* The property may change on the alive cluster. The placement driver manager 
has to handle configuration updates.
* The property should calculate two parameters: the lease interval and the long 
lease interval (LeaseUpdater#LEASE_INTERVAL, LeaseUpdater#longLeaseInterval). 
The frequency of checking leases is being evaluated based on the lease interval 
(LeaseUpdater#UPDATE_LEASE_MS).
* In addition to the tuning ability through the configuration framework, we 
should provide a configuration through system properties to use in tests. Add 
the system property for the lease interval only, because for the long lease 
interval, the property already exists.
* Do not forget to check TODOs.

*Definition of done*
Allow to configure lease intervat at least the system properties to use in the 
test.
Also, the ability to configure should be available through the Ignite property.

  was:
*Motivation*
Currently, the lease interval depends on the lease update frequency and is 
calculated like this:
{code:title=LeaseUpdater.java}
private static final long LEASE_INTERVAL = 10 * UPDATE_LEASE_MS;
{code}
The interval is impossible to configure; that way, it makes the test longer 
than it can be with a short lease interval.

*Implementation notes*
Do not forget to check TODOs.

*Definition of done*
Allow to configure lease intervat at least the system properties to use in the 
test.
Also, the ability to configure should be available through the Ignite property.


> Allow to configure lease interval
> ---------------------------------
>
>                 Key: IGNITE-20485
>                 URL: https://issues.apache.org/jira/browse/IGNITE-20485
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Vladislav Pyatkov
>            Priority: Major
>              Labels: ignite-3
>
> *Motivation*
> Currently, the lease interval depends on the lease update frequency and is 
> calculated like this:
> {code:title=LeaseUpdater.java}
> private static final long LEASE_INTERVAL = 10 * UPDATE_LEASE_MS;
> {code}
> The interval is impossible to configure; that way, it makes the test longer 
> than it can be with a short lease interval.
> *Implementation notes*
> * Create a new property root to configure. The property has to be specified 
> for the placement driver only (PlacementDriverConfigurationScema).
> * The property should be configured for the entire cluster 
> (ConfigurationType#DISTRIBUTED).
> * The property may change on the alive cluster. The placement driver manager 
> has to handle configuration updates.
> * The property should calculate two parameters: the lease interval and the 
> long lease interval (LeaseUpdater#LEASE_INTERVAL, 
> LeaseUpdater#longLeaseInterval). The frequency of checking leases is being 
> evaluated based on the lease interval (LeaseUpdater#UPDATE_LEASE_MS).
> * In addition to the tuning ability through the configuration framework, we 
> should provide a configuration through system properties to use in tests. Add 
> the system property for the lease interval only, because for the long lease 
> interval, the property already exists.
> * Do not forget to check TODOs.
> *Definition of done*
> Allow to configure lease intervat at least the system properties to use in 
> the test.
> Also, the ability to configure should be available through the Ignite 
> property.



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

Reply via email to